commit 5115311252f4910dd195002c54acb1bbb9e3b117
parent 5ffeff30bbf1e1d92028f9f7fc98c243ed7d4264
Author: pyratebeard <root@pyratebeard.net>
Date: Fri, 5 Jul 2024 15:45:29 +0100
colemak_final_boss
Diffstat:
1 file changed, 24 insertions(+), 0 deletions(-)
diff --git a/entry/colemak_final_boss.md b/entry/colemak_final_boss.md
@@ -1,3 +1,27 @@
Windows. Windows is the final boss in my Colemak journey, and I have final beaten it.
+My Colemak journey has ... [TK][colemak_exp] [TK][colemak_lvl_up] [TK][colemak_2]
+I used [AutoHotKey][autohotkey] and [Portable Keyboard Layout][portable_keyboard_layout].
+
+Without Admin access on my work laptop I was unable to install AutoHotKey. This worked as long as I remembered to start the app after logging in, but I couldn't use Colemak to log in.
+
+I had to upload the Portable Colemak app to each of the remote Windows systems, and when the remote screen locked I couldn't use Colemak to enter the password.
+
+While this worked enough to only slightly annoy me, the bigger issue was the inability to remap Capslock to Control and Escape
+
+Suddenly it dawned on me, could I do this in the firmware? The answer, yes.
+
+For both [Vial][vial] and [QWK][qmk] I could define a [Mod-Tap][mod_tap] key. 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?
+
+It turns out that this does exactly what I hoped, Colemak works on Windows at every level. On my Linux system is also means I don't need a custom keymap or the [xcape][xcape] tool.
+
+colemak_exp: 20220113-colemak_exp.html
+colemak_lvl_up: 20220214-colemak_lvl_up.html
+colemak_2: 20220825-colemak_+2.html
+autohotkey:
+portable_keyboard_layout:
+vial:
+qmk:
+mod_tap:
+xcape:
