Mapping Caps Lock to simultaneous Esc and Super (Mod4)

capslock_super_esc.md

Mapping Caps Lock to simultaneous Esc and Super (Mod4)

The CAPS key can be mapped to an escape key when pressed once, and a super (mod4) key when used in combination with other keys.

Create the file /usr/share/X11/xkb/symbols/custom_opts with the following:

// Make Caps an additional Escape
hidden partial modifier_keys
xkb_symbols "super_esc" {
    key <CAPS> { [ Escape ] };
    modifier_map Mod4 { <CAPS> };
};

Edit /usr/share/X11/xkb/rules/evdev and add a new line in the ! option = symbols section:

  custom:super_esc = +custom_opts(super_esc)

Edit /usr/share/X11/xkb/rules/evdev.lst and add a new line the ! option section:

  custom:super_esc  Make Caps Lock an additional ESC and Mod4

Restart your X session and apply the setting using your DE's keyboard layout options.

Updating the keyboard layout option

Gnome

Open dconf-editor, and navigate to org.gnome.desktop.input-sources. Add 'custom:super_esc' to the xkb-options list. For example, if you have no other options set, just use ['custom:super_esc']. If you have other options set, separate using commas like so: ['compose:ralt', 'custom:super_esc'].

You can also use the gsettings command to do this via commandline.

XFCE

Edit /etc/default/keyboard and add custom:super_esc to the XKBOPTIONS variable (comma-separated).

Other options

Most laptops have the alt key really close to the windows key, which can result in accidental keypresses. I like to use the altwin:alt_win xkb option (Alt is mapped to Win and the usual Alt) to make both keys work as alt.

This has been working for me but I just now realized that escape is always pressed even if i use it in combination with other keys. So for example, if I press <Caps>e, what will actually happen is <Esc><Super>e. This is also without even releasing the <Caps> key. While still holding the <Caps> key, <Esc> will already be initiated. Do you have the same behavior? Does anyone know how to fix this? Thanks.

I have not tried it yet to test it. Hope Ben Davis knows more about this.

…

On Fri, Jan 22, 2021, 16:33 mrkvn ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ This has been working for me but I just now realized that escape is always pressed even if i use it in combination with other keys. So for example, if I press <Caps>e, what will actually happen is <Esc><Super>e. This is also without even releasing the <Caps> key. While still holding the <Caps> key, <Esc> will already be initiated. Do you have the same behavior? Does anyone know how to fix this? Thanks. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://gist.github.com/e8cc8371499b52ac276fbe864247fdb7#gistcomment-3603610>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALVNTCM4OBXBEDULT7EEHPTS3GLFBANCNFSM4NBQJZLA> .

I have not tried it yet to test it. Hope Ben Davis knows more about this.

Thanks. I'm aware that if you press , it will be invoked even without releasing it so most probably it's the same behavior if you just move it to . But if there's a way to change that behavior, I would prefer that.

@mrkvn I've noticed the same thing with some applications, but not everywhere. I think it has to do with whether or no the application checks for "key down" vs "key pressed". It hasn't been enough of an issue for me to bother investigating it, but you might be able to get more info using xev to see exactly what keyboard events are being sent.

Just tried this: if I do ctrl-v at a terminal to capture the next key press I can see that escape (for me reported as the literal escape character ^[) is sent immediately on the key-down of capslock, i.e. before you even get to pressing the second key of the key-chord (which then also takes effect). So I suspect that escape is always being sent? As you say that may not be a problem should most applications simply choose to ignore it but perhaps at least one thing to be mindful of.