3 ms·
System Preferences > Accessibility > Keyboard > Navigation then enable full keyboard. The function has existed since at least 2002 when I started using OS X fu
by jen20 4y ago
System Preferences > Accessibility > Keyboard > Navigation then enable full keyboard.
The function has existed since at least 2002 when I started using OS X full time, though it did just take me almost 5 seconds to find the current location of it by googling (I enable it via defaults).
- bastawhiz 4y agoThere's also Preferences > Keyboard > Shortcuts > "Use keyboard navigation to move focus between controls" which is a separate thing (that arguably should be enabled by default).
- xbar 4y agoThey both should be. It's like shipping a set of scissors in a container that requires scissors to open.
- PeterWhittaker 4y agoCf my comment above re the limits of this approach.
- PeterWhittaker 4y agoWow, is that ever awful in terminal! Talk about poorly thought out. And it doesn't provide the feature I was inquiring about, accessing the menu bar, at least not AFAICT. I may be missing something. While I've had Macs for years, and mostly use the keyboard, I've simply accepted that some things require a mouse. It's the old tradeoff: current muscle memory works kinda well, is it worth research and retraining? Good, effective keyboard navigation is the ONLY thing I like about those times I have to use Windows. The trackpad is wrong, mouse scroll is wrong, so much is wrong, but being able to jump about without the mouse is really nice. (After using NextStep years (well, decades) ago and feeling personally triggered and antagonized by Steve's refusal to support PageUp/PageDown "because they are not pages" (no, they're screens dude, flex a bit, get real), I was pleasantly surprised that Mac OS supported PageUp/PageDown.