Somewhere along the way of installing various packages, the menu hot-key of ‘F’ for File was lost. To get to that menu option now it is necessary to press Alt+ and shift over using arrow keys.
Is there a simple way to restore ‘Alt+F’ as a shortcut for File in the menu bar?
Some package most likely added a key binding to “alt+f”, which now prevents you from focusing menu items with it.
Thank you for the input but this is not the reason. The combo ‘alt-f’ is not doing anything, I have the FindKeyConflicts plug-in installed and that does not identify a conflict. The closest a review of All Key Mappings comes to is [alt+f10], [alt+f2], [alt+f3], [alt+f5].
I genuinely think this is due to a plug-in rewriting the menu. The ‘F’ is no longer underlined in ‘File’ on the menu bar whereas all the other hot-keys appear as they should. Testing a theory that this shortcut was due to a key mapping conflict, I tested by remapping a shortcut to ‘alt+e’. The test worked in that it executed the short-cut instead of activating the Edit panel of the menu. There is no change in appearance of the Edit menu item when it a key conflict.
Still wondering
[quote=“FichteFoll”]Some package most likely added a key binding to “alt+f”, which now prevents you from focusing menu items with it.
Check with packagecontrol.io/packages/Edit%20Preferences[/quote]
This is the important information here. Yes, it is totally possible for packages to override default menu texts (and accidentally removing accelerators in the process). It’s not too easy to find the contender though because almost every package defines a “Main.sublime-menu” file.
I suggest checking the rendered File menu and trying to guess which package could have inserted menu items into it. Then see if disabling that package fixes the accelerator. Then file a bug report at the package’s repo and tell them to never override the “caption” (or basically anything) of a menu item that is provided by default.
FichteFoll,
Thank you for your input. I had to methodically go through Package Control.sublime-settings as a reference list and methodically removing each package and then reinstall it. I found the culprit. It was not necessary to file a bug report for upon re-installation the short-cut of ‘F’ in File came back.