Ctrl-K as prefix key? [Linux]


#1

Is there a specific reason why Ctrl-K is used as a prefix key? (and not Ctrl-X? I know it’s normally a cut key, but…)

Coming from Emacs, (I already have emacs-mode and emacs-flow installed) I can’t stop hitting Ctrl-K. I have already remapped Ctrl-K to a “Kill Line” method, but there is a short delay. I figured it was because it waits for a second key stroke.

If this functionality is intended, is there some way to unmap keys? Otherwise, I guess I will have to patch the Atom core.


#2

In the Keymaps documentation under “Removing Bindings”:

https://atom.io/docs/v0.96.0/advanced/keymaps


#3

Thanks for the tip.

However, once a prefix key is mapped, overriding it with ‘unset!’ still makes it apply as a command.

I tried a simple example:

'.workspace .editor:not(.mini)':
  'ctrl-u': 'editor:move-to-beginning-of-line'
  'ctrl-u j': 'editor:move-to-end-of-line'
  'ctrl-u j': 'unset!'

Here Ctrl-u waits for Ctrl-u j to happen although it’s unset. Ctrl-u j does nothing as intended, but the prefix key still waits for it to trigger.


#4

That sounds like a bug. Would you file it on the Atom Keymap package?


#5

What was the final solution to this? I want the exact same key, ctrl-k, but on Windows. I’m trying to get my Windows keys to match my main Mac development box.