This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
In the Options -> KeyMap, there are two pairs of actions with the same name and the same shortcuts EditorAction[Navigate to Next Occurrence:gsf-next-marked-occurrence] EditorAction[Navigate to Next Occurrence:java-next-marked-occurrence] One action comes from java/editor module, the second one from gsf. I suggest either change the name or merger the actions in one. Two same actions look strange and can be confusing for the user
Adding Tor to CC as a initial owner for ruby/gsf component
These actions won't be defined on the same mimetypes; java-next-marked-occurrence will occur in Java files, and gsf-next-marked-occurrence will occur in GSF-derived file types. Perhaps we can just change the action name to "next-marked-occurrence" in both Java and GSF? It would be even better if we could define this in the base editor, along with a keybinding, so we don't have to keep registering this across file types (as I understand this action is also available in the C/C++ support with its own implementation as well).
*** Issue 140437 has been marked as a duplicate of this issue. ***
See also Tools>Options>Keymaps, Project node... (If I wasn't used to this, I would be pretty confused...)
Created attachment 68983 [details] screenshot
joshis: the duplicated project related actions are likely unrelated to the original report - please file a new report against the projects infrastructure.
The new look of Options->Keymap does not exhibit the original problem so closing as fixed.