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
I was told this was noticed in the past and someone found a local fix for it, but I couldn't find it in the JIRA issues, so I'm going to refile this.
I have a Kepler instance which is working fine. I installed STS 3.6.4, which is Luna. I have them configured just about the same, as much as possible, with the same plugins.
At some point I discovered that some key bindings in my Groovy views were missing, like "quick outline", "go to line", and "next word". I first noticed this with "quick outline", and I think it's likely that others besides those other two are missing.
It isn't just that the bindings went missing. I tried to readd the binding for "quick outline", and it just doesn't work. I even brought up both Eclipse instances side by side (connected to different workspaces), and the "Quick Outline" function in "Keys" is bound exactly the same in both.
I also have the Emacs+ plugin in both instances. Using this, I can directly execute these unbound functions. Running "go-to-line" and "next-word" works fine, but when I execute "quick-outline", I see the dialog appear and disappear in a fraction of a second.
Although I can't get to "quick-outline", the normal outline view appears to render fine, and when I double-click on an entry in that, the editor view goes to that symbol.
When I view a Java file in the Luna instance, the behavior is similar, but slightly different. When I press Ctrl+o, I see a little box show up in the bottom right-hand corner of the Eclipse window that just shows "Quick Outline Ctrl+O". This is the box that shows up when I press the beginning of a key sequence where there are multiple possible sequences that start with that sequence.
When I do this in the Java view, I also saw log entries appear that are definitely relevant, but I can't fully interpret them. I'll include the entire log, but this is the relevant excerpt:
!MESSAGE A conflict occurred for CTRL+O:
Binding(CTRL+O,
ParameterizedCommand(Command(org.eclipse.mylyn.task.ui.editor.QuickOutline,Quick Outline,
Show the quick outline for the editor input,
Category(org.eclipse.mylyn.tasks.ui.commands,Task Repositories,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@7b3d759f,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.jdt.ui.javaEditorScope,,,user)
Binding(CTRL+O,
ParameterizedCommand(Command(org.eclipse.pde.ui.quickOutline,Quick Outline,
Open a quick outline popup dialog for a given editor input,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@a4479f1,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.jdt.ui.javaEditorScope,,,user)
Binding(CTRL+O,
ParameterizedCommand(Command(org.eclipse.wst.jsdt.ui.edit.text.java.show.outline,Quick Outline,
Show the quick outline for the editor input,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@73b1c6d9,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.jdt.ui.javaEditorScope,,,user)
Binding(CTRL+O,
ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.show.outline,Quick Outline,
Show the quick outline for the editor input,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@1e1634fa,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.jdt.ui.javaEditorScope,,,user)
Binding(CTRL+O,
ParameterizedCommand(Command(org.eclipse.wst.sse.ui.quick_outline,Quick Outline,
Show the quick outline for the editor input,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@7c94a0dc,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.jdt.ui.javaEditorScope,,,user)
I decided to try to reset my keys to default bindings. This actually fixed Ctrl+o in my Java view. The Groovy view still doesn't respond to either of the three commands I was focusing on, and executing "quick-outline" directly in EITHER view makes the dialog appear and disappear in a fraction of a second. I suppose the fact that this last behavior also happens in the Java view, where the regular Ctrl+o press works fine, tells me that the quick appearance and disappearance has something to do with executing the function manually, as opposed to with a keypress.
I also note the following log entries:
!ENTRY org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Warnings while parsing the key bindings from the 'org.eclipse.ui.commands' extension point
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.springframework.ide.eclipse.beans.ui', id='org.springframework.ide.eclipse.beans.ui.inplace.show'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.springframework.ide.eclipse.boot.launch', id='org.springsource.ide.eclipse.boot.BootLaunchShortcut.run'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.springframework.ide.eclipse.boot.launch', id='org.springsource.ide.eclipse.boot.BootLaunchShortcut.debug'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.springsource.ide.eclipse.gradle.ui', id='org.springsource.ide.eclipse.gradle.ui.refresh.all'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.refactoring', id='org.codehaus.groovy.eclipse.refactoring.command.inlineMethod'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.refactoring', id='org.codehaus.groovy.eclipse.refactoring.command.inlineMethod'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.refactoring', id='org.codehaus.groovy.eclipse.refactoring.command.rename'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.792
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.refactoring', id='org.codehaus.groovy.eclipse.refactoring.command.rename'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.792
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.ui', id='org.codehaus.groovy.eclipse.groovyScriptLaunchShortcut.run'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.792
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.ui', id='org.codehaus.groovy.eclipse.groovyScriptLaunchShortcut.debug'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.792
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.ui', id='org.codehaus.groovy.eclipse.ui.convertToMethod'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.792
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.ui', id='org.codehaus.groovy.eclipse.ui.convertToClosure'
The text was updated successfully, but these errors were encountered:
I was told this was noticed in the past and someone found a local fix for it, but I couldn't find it in the JIRA issues, so I'm going to refile this.
I have a Kepler instance which is working fine. I installed STS 3.6.4, which is Luna. I have them configured just about the same, as much as possible, with the same plugins.
At some point I discovered that some key bindings in my Groovy views were missing, like "quick outline", "go to line", and "next word". I first noticed this with "quick outline", and I think it's likely that others besides those other two are missing.
It isn't just that the bindings went missing. I tried to readd the binding for "quick outline", and it just doesn't work. I even brought up both Eclipse instances side by side (connected to different workspaces), and the "Quick Outline" function in "Keys" is bound exactly the same in both.
I also have the Emacs+ plugin in both instances. Using this, I can directly execute these unbound functions. Running "go-to-line" and "next-word" works fine, but when I execute "quick-outline", I see the dialog appear and disappear in a fraction of a second.
Although I can't get to "quick-outline", the normal outline view appears to render fine, and when I double-click on an entry in that, the editor view goes to that symbol.
When I view a Java file in the Luna instance, the behavior is similar, but slightly different. When I press Ctrl+o, I see a little box show up in the bottom right-hand corner of the Eclipse window that just shows "Quick Outline Ctrl+O". This is the box that shows up when I press the beginning of a key sequence where there are multiple possible sequences that start with that sequence.
When I do this in the Java view, I also saw log entries appear that are definitely relevant, but I can't fully interpret them. I'll include the entire log, but this is the relevant excerpt:
!MESSAGE A conflict occurred for CTRL+O:
Binding(CTRL+O,
ParameterizedCommand(Command(org.eclipse.mylyn.task.ui.editor.QuickOutline,Quick Outline,
Show the quick outline for the editor input,
Category(org.eclipse.mylyn.tasks.ui.commands,Task Repositories,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@7b3d759f,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.jdt.ui.javaEditorScope,,,user)
Binding(CTRL+O,
ParameterizedCommand(Command(org.eclipse.pde.ui.quickOutline,Quick Outline,
Open a quick outline popup dialog for a given editor input,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@a4479f1,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.jdt.ui.javaEditorScope,,,user)
Binding(CTRL+O,
ParameterizedCommand(Command(org.eclipse.wst.jsdt.ui.edit.text.java.show.outline,Quick Outline,
Show the quick outline for the editor input,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@73b1c6d9,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.jdt.ui.javaEditorScope,,,user)
Binding(CTRL+O,
ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.show.outline,Quick Outline,
Show the quick outline for the editor input,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@1e1634fa,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.jdt.ui.javaEditorScope,,,user)
Binding(CTRL+O,
ParameterizedCommand(Command(org.eclipse.wst.sse.ui.quick_outline,Quick Outline,
Show the quick outline for the editor input,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@7c94a0dc,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.jdt.ui.javaEditorScope,,,user)
I decided to try to reset my keys to default bindings. This actually fixed Ctrl+o in my Java view. The Groovy view still doesn't respond to either of the three commands I was focusing on, and executing "quick-outline" directly in EITHER view makes the dialog appear and disappear in a fraction of a second. I suppose the fact that this last behavior also happens in the Java view, where the regular Ctrl+o press works fine, tells me that the quick appearance and disappearance has something to do with executing the function manually, as opposed to with a keypress.
I also note the following log entries:
!ENTRY org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Warnings while parsing the key bindings from the 'org.eclipse.ui.commands' extension point
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.springframework.ide.eclipse.beans.ui', id='org.springframework.ide.eclipse.beans.ui.inplace.show'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.springframework.ide.eclipse.boot.launch', id='org.springsource.ide.eclipse.boot.BootLaunchShortcut.run'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.springframework.ide.eclipse.boot.launch', id='org.springsource.ide.eclipse.boot.BootLaunchShortcut.debug'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.springsource.ide.eclipse.gradle.ui', id='org.springsource.ide.eclipse.gradle.ui.refresh.all'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.refactoring', id='org.codehaus.groovy.eclipse.refactoring.command.inlineMethod'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.refactoring', id='org.codehaus.groovy.eclipse.refactoring.command.inlineMethod'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.791
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.refactoring', id='org.codehaus.groovy.eclipse.refactoring.command.rename'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.792
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.refactoring', id='org.codehaus.groovy.eclipse.refactoring.command.rename'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.792
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.ui', id='org.codehaus.groovy.eclipse.groovyScriptLaunchShortcut.run'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.792
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.ui', id='org.codehaus.groovy.eclipse.groovyScriptLaunchShortcut.debug'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.792
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.ui', id='org.codehaus.groovy.eclipse.ui.convertToMethod'
!SUBENTRY 1 org.eclipse.ui 2 0 2015-04-05 14:31:24.792
!MESSAGE Cannot bind to an undefined command: plug-in='org.codehaus.groovy.eclipse.ui', id='org.codehaus.groovy.eclipse.ui.convertToClosure'
The text was updated successfully, but these errors were encountered: