Your Best Key Has the Worst Job

The key I'm talking about is Caps Lock.

It sits in one of the best spots on the keyboard: big, easy to reach, right next to A, under your left pinky.

And most of the time, its job is to ruin a sentence.

LIKE THIS. A NORMAL THOUGHT SUDDENLY LOOKS LIKE A CUSTOMER SUPPORT INCIDENT.

Then you turn it off, delete the sentence, and type it again.

That's a terrible job for a key this good.

How I noticed the problem

I started caring about this when I started using tmux.

tmux is a terminal multiplexer. It lets you keep sessions, windows, and panes running inside the terminal. Almost everything in tmux starts with a prefix key, and mine is Ctrl-a.

On paper, Ctrl-a is great. a is on the home row, right under my left hand.

In practice, with Control in the bottom-left corner of a normal keyboard, it felt awful.

Every tmux command started with the same uncomfortable motion: move my pinky down to Control, press it, hit a, then hit the actual command.

Split a pane. Switch windows. Detach from a session. Rename something. Move around. Same awkward reach every time.

The problem wasn't tmux. The problem was the keyboard.

Caps Lock was sitting right next to A, doing basically nothing. If that key were Control, Ctrl-a would stop being a stretch and become a tiny movement.

So I made it Control.

That was the first time tmux felt natural to me.

The mismatch

The pattern became obvious:

• Caps Lock is easy to reach and rarely useful
• Control is useful everywhere and awkward to reach
• Escape is useful constantly in modal editors and awkward to reach

So I don't let it be Caps Lock.

On my keyboards, that key does this:

• Tap: Esc
• Hold: Ctrl

It's the first keyboard change I make on every machine.

Tap for Escape, hold for Control

After moving Control to Caps Lock, making the same key Escape on tap felt obvious.

I spend a lot of time in Neovim. Escape is not an occasional key there. It's part of the editing loop: enter insert mode, type, leave insert mode, move, edit, repeat.

The default Escape key is far away. Caps Lock is already under my finger.

The pairing works because the keys have opposite shapes:

• Escape is a tap: press once, leave the mode
• Control is a hold: hold it while pressing something else

So one physical key can handle both jobs without feeling overloaded.

Tap to leave a mode. Hold to modify another key.

No new layer. No weird chord. Just a better job for a key I wasn't using.

Not a new idea

This might sound like a weird custom setup, but it is closer to an old default than a new trick.

Older Unix keyboards often had Control where modern keyboards put Caps Lock.

The ADM-3A mattered for vi in ways you can still feel today. Its H, J, K, and L keys had arrow labels printed on them, which is where vi-style hjkl navigation comes from. Its Control key also lived where modern keyboards put Caps Lock.

The shortcuts survived. The keyboard changed.

So the remap never felt like a clever hack to me. It felt like fixing a bad default.

How to try it

You don't need a custom keyboard to try this.

On macOS, the easy version is built in: make Caps Lock behave as Control in System Settings -> Keyboard -> Keyboard Shortcuts -> Modifier Keys. That alone gets you most of the benefit.

For the full tap/hold behavior, I first used Karabiner-Elements on a regular Mac keyboard.

Even its icon hints at the same idea: Esc where modern keyboards put Caps Lock.

These days I use ZMK on my Kinesis Advantage 360.

Different keyboard, same remap. That's usually how I know a setup change actually mattered.

On other systems, people use tools like Kanata, keyd, caps2esc, AutoHotkey, QMK, or ZMK. The tool matters less than the behavior: tap for Escape, hold for Control.

The only downside

The only downside is using someone else's keyboard.

I don't notice the remap when it's there. I notice it immediately when it isn't.

I hit Caps Lock expecting Control, and nothing happens. Or worse, I accidentally turn Caps Lock on and remember what the key was supposed to do.

That's the real cost of fixing a default: broken keyboards start feeling more broken.

But that's how you know it works. The moment a default disappears from your awareness is the moment it starts feeling correct.

Caps Lock never did. This remap does.