3 ms·

> What is the cost of remembering that Firefox starts with an F? Collisions and inconsistent mnemonics. Consider OP's shortcuts for Firefox, Finder, Typora, &

> What is the cost of remembering that Firefox starts with an F? Collisions and inconsistent mnemonics. Consider OP's shortcuts for Firefox, Finder, Typora, & iTerm. OP went with 'f', '\', 'y', and 't'. -- It's more complicated than just "remember the first letter of the app name". For something as infrequent as "open firefox" (I'm going to open the web browser at the start of my session, & never need to reopen it), it's not worth it. Whereas, say, "open note taking app" is more likely to be worth assigning such a shortcut to. > QMK is more limited in the area of rich text input and some other OS integration beyond low-level remapping Yeah, it generally isn't going to cover OS-specific integration. Though you can still send keys. e.g. I like using the 'cv' and 'm,' keys for "desktop left" and "desktop right". And that can be achieved with QMK.

eviks 4y ago
> Consider OP's shortcuts for Firefox, Finder, Typora, & iTerm. Why would you consider them? Make your own and stop at the X number of apps where it becomes confusing. Also, for the top-5 most frequent apps the F=Firefox is irrelevant, you'll remember any combo, so just pick the most convenient (e.g., home row keys), the cost of training the muscle memory is almost none. The infrequent apps can be hidden behind a chord, but then that is best achieved with visual cues (you can use system notifications for that with goku or even better KM app for better UI) Re. launching Firefox - you've missed the huge part of the switching-to-firefox workflow (it's not just launching the app, the same key switches to an existing app), that is very frequent and definitely worth a shortcut (even though, see my other comment, KM is much better for this task)