-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use Undo in Eclipse #432
Comments
As I know by default in key bindings the 'undo' is defined for table context. So I changed this behavior to 'content for source page'. Hope it will help you) |
I installed some updates in Eclipse Marketplace that were not automatically installed, EGradle Editor was one of those IIRC. It seems that the Undo option works now. RED was not updated, so maybe was related to some dependencies some dependencies. @NikitaOstr Thanks for the tip! I will try that, if this stops working again. |
This is still an issue. @NikitaOstr suggestion does not help. In fact I get an execution exception when I change the key binding values. `eclipse.buildId=4.21.0.I20210906-0500 org.eclipse.e4.ui.workbench org.eclipse.core.commands.ExecutionException: Error executing 'org.robotframework.ide.eclipse.undoInTable': org.eclipse.e4.core.di.InjectionException: Unable to process "E4UndoHandler#undo()": no actual value was found for the argument "RobotEditorCommandsStack". |
Agreed, it's weird: |
Eclipse version:
Eclipse IDE for Enterprise Java and Web Developers (includes Incubating components)
Version: 2021-09 (4.21.0)
Build id: 20210910-1417
OS: Windows 10, v.10.0, x86_64 / win32
Java vendor: Oracle Corporation
Java runtime version: 15.0.1+9-18
Java version: 15.0.1
Latest RED Version available in the Marketplace.
I cannot use the Undo/Ctrl+z feature in Eclipse. It works just fine in other editors, such as Python Editor or Text Editor, but in RED it's disabled.
It has been happening for quite some time already, even in previous Eclipse versions.
Is this some configuration that I don't have enabled, or is it a bug in RED?
The text was updated successfully, but these errors were encountered: