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.
Product Version: NetBeans IDE 8.0.2 (Build 201411181905) Updates: NetBeans IDE is updated to version NetBeans 8.0.2 Patch 1 Java: 1.8.0_25; Java HotSpot(TM) 64-Bit Server VM 25.25-b02 Runtime: Java(TM) SE Runtime Environment 1.8.0_25-b18 System: Windows 7 version 6.1 running on amd64; Cp1250; pl_PL (nb) I have an Eclipse profile for keymap and I want to define F2 as a shortcut for "Next Bookmark" action. First I'm checking F2 bindings, which are: * "Show Documentation Popup" in category "Other" * "Rename..." in category "System" That's ok for me - the Documentation Popup has another shortcut (Shift+F2), so I don't need two of them. The "Rename" is in different category, so it shouldn't collide with editor. I'm trying to define F2 for the Next Bookmark, and it says, that two actions conflict with the new assignment. Now the only choices are: - remove old ones, but BOTH of them will be removed - do not remove old ones, but the new assignment will be canceled It's not possible to keep the "Rename" shortcut in "System" category, which shouldn't conflict with the "Next Bookmark" action.
Created attachment 153056 [details] F2 assignments in the Eclipse profile
Created attachment 153057 [details] Message about the conflicting shortcut
Created attachment 153058 [details] Missing rename shortcut after adding next bookmark one
Actually an API deficiency. The next/prev bookmark actions are defined as global action with no indication they work exclusively with the editor. And to be precise, they do not - the next bookmark works even in another window and applies to the topmost editor; in this sense, it really clashes with the "Rename" global action. Passing to editor action component for evaluation as an enhancement: if it should be implemented, we need either to redefine the current Action categories with respect to the action scopes or provide a different categorization, so the Key Binding component can check for clashes just between actions with the same scope, not peers.