-
Notifications
You must be signed in to change notification settings - Fork 60
Conflicting keybinding for Open Type #38
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
Comments
same for rename
https://bugs.eclipse.org/bugs/show_bug.cgi?id=578135 |
I installed Eclipse EE 2022-12, and now when I try to find a Java class using But oddly if I My error log shows
This bug is very problematic, as "Open Type" via |
Hello,
What file is open while you're trying Ctrl+Shift+T ?
|
Just a normal Java source file. Whenever I open Eclipse for the first time, it exhibits this bug. I can switch tabs to other Java source file, and I still get a menu every time I hit It feels like there is a bug in Eclipse EE 2022-12 that gets confused as to the context upon startup, and somehow |
OK. And is the Java source opened in the Java editor or in the Generic Editor? Do you have other plugins installed that are supposed to provide Java assistance? The Ctrl+Shift+T handler from LSP4E shouldn't be participating at all unless there is a language server bound to .java files, and IIRC there is not such one by default in Eclipse packages. |
The Java editor. And once the
I am using the exact EE distribution for 2022-12:
Exactly. And that's why this is a bug. |
Maybe a duplicate of #164 |
Not exactly. #164 is about a logged message (which should be removed in Platform by the way); Here there is another preliminary issue: what does configure LSP4E to be active on .java files; this is not much intended in the EPP packages as far as I know. The EPP package needs to be investigated first. |
Saw this for the first time, after Eclipse upgraded itself to:
I can confirm the previous comments...
|
What is the language server that is bound to Java files and contributes to Ctrl+Shift+T? |
I've never deliberately started any language-server-backed-editor. (Yet - very interested in that though.) How would I find out? |
I don't think it would be deliberate. Can you please share the content of the "Language Servers" preference page and see what is bound to Java files? |
It's not just |
recently upgraded to 20221201-1913 and seeing same issues for both (Alt + Shift + R) and (Ctrl + Shift + T). Thanks for tip on ctrl clicking which clears it up temporarily |
Same here, Alt-Shift-R and Ctrl-Shift-T do not work. Version: 2022-12 (4.26.0) |
I tried the following:
So I cannot reproduce the issue. Can someone provide detailed steps to reproduce, from a fresh download and unzip of the package? |
Same steps as yours, but using the 2022-12 IDE For Committers Edition, produces it. (In also a new workspace.) |
I did the very same than you did, except it was with the windows version:
|
I just wanted to write the exact same thing. With windows eclipse-java-2022-12-R-win32-x86_64.zip I can reproduce both key binding issues. For the Shift+Alt+R problem it's even weirder on my machine. When I press those keys in a Java editor on a Java type name the entire workbench window starts to flicker for about 5 seconds until it pops up the conflict notification in the very top left corner of my monitor (outside of Eclipse). For me the two problems started all of a sudden yesterday in an existing installation/workspace. Please please please give me back the behavior that my fingers are used to for the last two decades! When you need more information then please let us know ASAP... |
OOmp Eclipse (https://github.com/eclipse-platform/.github/blob/main/CONTRIBUTING.md). When you click ctrl+shift+T the first time the dialog appears. After selecting Open Type once, it does not appear anymore. |
I'm closing this in LSP4E, it's more properly actionable on JDT end: eclipse-platform/eclipse.platform.ui#513 (comment) |
Note that additionally to having a proposal to ensure the JDT editor uses the right command for the binding, LSP4E also has received many improvements, currently only available in snapshots, that can have a postiive impact on this issue. So please try installing LSP4E snapshots. A release may take place later this week or next week. |
On Eclipse bugzilla the issue was: https://bugs.eclipse.org/bugs/show_bug.cgi?id=527785
A conflict occurred for CTRL+SHIFT+T:
Binding(CTRL+SHIFT+T,
ParameterizedCommand(Command(org.eclipse.lsp4e.symbolinworkspace,Go to Symbol in Workspace,
,
Category(org.eclipse.lsp4e.category,Language Servers,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@101eb529,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
Binding(CTRL+SHIFT+T,
ParameterizedCommand(Command(org.eclipse.jdt.ui.navigate.open.type,Open Type,
Open a type in a Java editor,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@6a9b8f33,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
The text was updated successfully, but these errors were encountered: