![]() We are going to walk through creating a system to bring uniformity to our apps with a single set of keyboard shortcuts. What if you could eliminate that switching cost? What if switching apps, rather than forcing you to learn new shortcuts, instead reinforced your muscle memory for the shortcuts you already know? In short, what if all of your apps felt the same? So, what happens when you try out a new app, and its keyboard shortcuts don’t align with your muscle memory? You could work on memorizing a whole new set of shortcuts, but then you face a cost of switching every time you change apps. You've likely memorized many of the shortcuts of your most used apps and, somewhere during this process, repetition has given way to muscle memory, making these shortcuts feel like second nature. But you're probably also aware that most of the apps you use on a daily basis provide keyboard shortcuts to increase the efficiency of routine tasks. You likely use a combination of your mouse and keyboard to interact with your computer throughout the day. There are some text snippet expansion methods, but nothing to simply modify keys.If you’re reading this, odds are you work on a computer. It would make sense to look into using Spacehammer and more VIM bindings sometime soon. However, Hammerspoon is one of the more promising configuration systems especially considering the more complete VIM bindings which exist in the community and would bear a second look. For my purposes right now, this monolithic a is enough, and the entire configuration corresponds to this commit in my Dotfiles. On the other hand, it is baffling to see the lack of good FOSS tools on this ecosystem 9, but that is to be expected perhaps. In that regard, this post is a success story, even with the awkwardness of the implementation. It has been very restrictive to not be able to use the keyboard layout I spent years crafting. 2) don’t really allow for more than downloading rules off of the internet 5, like the one below.ġ 3 Conclusions This is setup through a karabiner.json file, since it appears that the “Complex modifications” referred to in the GUI (Fig. I have been using the basic Colemak layout with a simplistic Karabiner caps to delete for a while now, which allows for a standards compliant Colemak experience, but extending this like I needed was a little bit of a struggle.Īpparently it is possible to overload the keyboard system with a “Hyper” key 4, which is the closest to Extend. Of Ukelele and manually writing things then, nothing more need be said. Also, rapid prototyping was out of the question, since Ukelele requires a log-out log-in cycle to set things up. The closest possible solution would be to do a very awkward Esc based layout. It can either be remapped using system settings 3 to one of the other modifier keys, but not to Extend. However, evidently, there is no real way to remove the stickiness from the Caps Lock key. Now of the four, I had a predilection to move towards manually writing, with the help of Ukelele. keylayout files Use Karabiner Elements This seems to be closer to AutoHotKey and the like, runs in the background and actively intercepts keys based on json configurations though there seems to be a more rational method (a hidutil remapping file generator) for newer kernels 2 Script things with Hammerspoon Uses a lua engine to interact with the system, can be configured for the most part with Fennel using Spacehammer keylayout These then go in $HOME/Library/Keyboard\ Layouts Use Ukelele The incredibly poorly named (for search purposes) versatile tool is able to ease the pain slightly for writing. There are essentially a few options: Manually write. Just as a reminder, my setup (or hzColemak) consists of an augmented VIM workflow, as shown below, and described in my previous post. HAMMERSPOON CAPS LOCK ESCAPE AND CONTROL SERIESThis post is part of a series on Colemak and keyboard management in general. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |