You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: I am using CTRL+SHIFT+T more than 17 years now to show the "Open type" dialog in eclipse when writing Java code. But now there is a name clash : The language server parts have introduced same short cut for "Go to Symbol in Workspace". Because of this situation there is always a selection inside the window necessary which variant shall be used when pressing the shortcut inside a Java editor - very annoying/slowing down workflow.
I originally made an issue at JDT - see eclipse-jdt/eclipse.jdt.ui#394 but it is more something that comes from lsp4e, so it should be addressed here.
Details
Wanted
As a user I do not want to have always a selection prompting/a clash between those two parts
Suggestion
If the keyboard binding for lsp4e would not be for the complete window but only inside the generic editor this would be more suitable.
I did change my own preferences in following way and it works well for me.
It would be nice if the initial setup from lsp4e would produce no binding problems.
The text was updated successfully, but these errors were encountered:
Situation
I upgraded my eclipse IDE to:
(I did not have the problem with 2022-09)
Problem: I am using
CTRL
+SHIFT
+T
more than 17 years now to show the "Open type" dialog in eclipse when writing Java code. But now there is a name clash : The language server parts have introduced same short cut for "Go to Symbol in Workspace". Because of this situation there is always a selection inside the window necessary which variant shall be used when pressing the shortcut inside a Java editor - very annoying/slowing down workflow.I originally made an issue at JDT - see eclipse-jdt/eclipse.jdt.ui#394 but it is more something that comes from lsp4e, so it should be addressed here.
Details
Wanted
As a user I do not want to have always a selection prompting/a clash between those two parts
Suggestion
If the keyboard binding for lsp4e would not be for the complete window but only inside the generic editor this would be more suitable.
I did change my own preferences in following way and it works well for me.
It would be nice if the initial setup from lsp4e would produce no binding problems.
The text was updated successfully, but these errors were encountered: