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.
1. Go to NetBeans -> Preferences -> Keymap You see that the shortcut descriptions use the "Meta" word. I think this should be changed to "Cmd", as "Meta" seems to be deprecated and "Cmd" is the preferred new equivalent, see: http://en.wikipedia.org/wiki/Command_key Or better yet, could the graphical "Gordon loop" symbol be used? (And same for the graphical symbol representing the Alt key.)
Fixed: http://hg.netbeans.org/core-main/rev/1307e20d4647 The graphical symbols for Cmd and Alt keys are used
Created attachment 119594 [details] Screenshot of the options dialog Weird, still does not work for me in build web-main #7654, which already contains this change. See the attached screenshot.
Weird indeed. I tested it yesterday on a Mac and it was showing the graphical symbols. I will have another look on Monday as I do not have access to a Mac now.
Integrated into 'main-golden', will be available in build *201205180400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/1307e20d4647 User: Theofanis Oikonomou <theofanis@netbeans.org> Log: Issue #212599 - Use Cmd rather than Meta in shortcut descriptions
I can reproduce the screen shot in jdk1.7.0_04. If I am using jdk1.6.0_31 I can see the icon symbols and not the Meta/Alt words. Reassigning to jdk problems
I confirm I have the same behavior, reopening.
Also note issue #205820: the code that performs KeyStroke-to-human-readable conversion is duplicated in Editor Settigns Storage and Keymap Options, and does not work exactly the same. I suggest that Keymap Options exports these utility methods as an API, so we have one place with ultimate responsibility for Keystroke presentation. Also I could blame the Shortcut Finder API, which transfers the keystroke in a human-readable form, instead of Emacs portable one.
Oops, wrong issue number; the correct relevant issues are issue #213201 and issue #213422