pyratelog

personal blog
git clone git://git.pyratebeard.net/pyratelog.git
Log | Files | Refs | README

20240705-colemak_final_boss.md (2715B)


      1 Windows. Windows is the final boss in my Colemak journey, and I have finally beaten it.
      2 
      3 My Colemak journey started a couple of [years ago][colemak_exp].  After a bit of [learning][colemak_lvl_up] and overcoming some [issues][colemak_2] I have been happily using Colemak on my Linux system full time.
      4 
      5 For work however, things have not been quite so comfortable.  I have [ranted][a_penguin_at_the_window] about trying to use Colemak on Windows for work before.  The best option I found was to use [AutoHotKey][autohotkey] and [Portable Keyboard Layout][portable_keyboard_layout].
      6 
      7 Without Admin access on my work laptop I had some issues with getting the AutoHotKey Colemak script running, although using Portable Keyboard Layout worked.  Or at least it worked as long as I remembered to start the app after logging in.  It doesn't work at the login screen so I had to use the laptop's keyboard for that.
      8 
      9 Prior to actually doing any work I had to upload the Portable Colemak app to each of the remote Windows systems I access, yet when the remote screen locked I couldn't use Colemak to enter the password so had to use the laptop's keyboard again.
     10 
     11 While this worked enough to only slightly annoy me on a daily basis, the bigger gripe was the inability to remap Capslock to Control and Escape.  On Linux I have been doing this using the [xcape][xcape] tool, there is no way of achieving the same in Windows that I've found (without admin access).
     12 
     13 Then one morning it suddenly dawned on me, could I do this in the keyboard firmware?  The short answer, yes.
     14 
     15 For both my custom keyboards, one using [VIA/QMK][via] and the other [ZWK][zmk], I could define a Mod-Tap key to replace Capslock with Control/Escape.  This was a game changer for my work system and also got me thinking, what would happen if I configure Colemak at the firmware level?
     16 
     17 It turns out that this does exactly what I hoped.  Colemak now works on Windows at every level without any apps or config changes.  The same is true on my Linux system, which means I don't need my custom keymap or the xcape tool.
     18 
     19 Irritatingly this didn't occur to me before, but modifying the firmware has made working in Windows so much better as well as allowing me to cut out some config changes from my Linux system.
     20 
     21 Windows smashed, finally.
     22 
     23 [colemak_exp]: 20220113-colemak_exp.html
     24 [colemak_lvl_up]: 20220214-colemak_lvl_up.html
     25 [colemak_2]: 20220825-colemak_+2.html
     26 [a_penguin_at_the_window]: 20230929-a_penguin_at_the_window.html
     27 [autohotkey]: https://www.autohotkey.com/
     28 [portable_keyboard_layout]: https://pkl.sourceforge.net/
     29 [xcape]: https://github.com/alols/xcape
     30 [via]: https://docs.qmk.fm/mod_tap#mod-tap
     31 [zmk]: https://zmk.dev/docs/behaviors/mod-tap