Resources in the network (1, 2, 3) claim that some key combinations, among which Ctrl-Shift-letter, Ctrl-number, Ctrl-i/Tab, Ctrl-m/Enter, Esc/Ctrl-[, cannot be mapped reliably in Vim because the terminal does not distinguish them from their unmodified counterparts (more background in this Gilles' answer and this ASCII table article). As a concrete example, the maps

nnoremap <Tab>   :!echo A<CR>
noremap  <C-S-X> :!echo B<CR>
noremap  <C-1>   :!echo C<CR>
noremap  <C-F1>  :!echo D<CR>

cause both Tab and Ctrl-i to print A (also in Gvim) and both Ctrl-x and Ctrl-Shift-x to print B. Ctrl-{1,2,...} and Ctrl-{F1,F2,...} cannot be mapped, the former not even in Gvim.

This answer to "How to map Ctrl-a and Ctrl-Shift-a differently?" shortly describes a solution for Xterm, but it lacks several tricky details that may escape some. This is an attempt to provide a more complete answer.

Although this is a Vim centered question, other terminal applications with customizable mappings can also benefit from it. Vifm is an obvious case.

  • I used to remapping <Tab>, now I afraid of it.
    – Niing
    Commented Apr 2, 2021 at 23:03
  • 1
    @Niing I suppose you didn't notice you relinquished Ctrl-i when doing that?
    – Quasímodo
    Commented Apr 3, 2021 at 10:22

1 Answer 1


I'll start with Xterm because it is the most complicated one. Kitty and Urxvt are tackled at the end.


The ~/.Xresources file configures Xterm (and some other Xlib applications). Whenever you are done editing it, issue xrdb ~/.Xresources and open a new Xterm to test the changes. Start with

XTerm*metaSendsEscape: true
XTerm*eightBitInput:   false

See man xterm or configuring Xterm for further options, such as colors and fonts — the defaults are admittedly ugly.

Sending keycodes

We will follow Leonerd's article proposal, and have the terminal send CSI codepoint;modifier u, where

  • CSI stands for an Esc character followed by [.

  • codepoint is the decimal Unicode value of the character to be mapped. ASCII characters have the same decimal representation in Unicode.

  • modifier is chosen from the table below:

    None Shift Alt Alt+Shift Ctrl Ctrl+Shift Ctrl+Alt Ctrl+Alt+Shift
    1 2 3 4 5 6 7 8


Look up X in an ASCII table and find that its decimal value is 88. Therefore CSI 88;5 u should be sent to Vim. This goes in .Xresources:

XTerm*Translations: #override\
    Ctrl ~Meta  Shift <Key>x   :string("\033[88;5u")

Ctrl-Shift-x now produces the sequence in quotes. A tilde negates the modifier, i.e., ~Meta means that Alt is not pressed (Meta means Alt). 033 is Esc in octals.

There should be no spaces after the backslashes (Xrdb would warn you of the mistake) and, as will be seen ahead, multiple bindings should be separated from each other with \n\.

Tab and Ctrl-i

i is decimal 105 and Tab is decimal 9, but both Ctrl-i and Tab send 9, as the ASCII table article explains. So Ctrl-i must send a different sequence to disambiguate them, and by the same reasoning as before, we conclude it is CSI 105;5 u.

XTerm*Translations: #override\
    Ctrl ~Meta ~Shift <Key>i   :string("\033[105;5u")

One could also add ~Ctrl ~Meta ~Shift <Key>Tab :string("\011") but that would be redundant since Tab already sends decimal 9 (octal 11).

Modified Tab is special as listed under "Modified C0 controls".

XTerm*Translations: #override\
   ~Ctrl ~Meta  Shift <Key>Tab :string("\033[Z")    \n\
    Ctrl ~Meta ~Shift <Key>Tab :string("\033[9;5u") \n\
    Ctrl ~Meta  Shift <Key>Tab :string("\033[1;5Z")

More special keys

Here belong F1-F12, Home and others. In Xterm they already have unambiguous codes, which can be straightforwardly determined by pressing Ctrl-vKey in Vim's insert mode. For example, Ctrl-vCtrl-F1 produces <ESC>[1;5P.


Now we just have to add the bindings to .vimrc:

" Disambiguate Tab and Ctrl-i
nnoremap <ESC>[105;5u <C-I>

nnoremap <Tab>        :!echo A<CR>
noremap  <ESC>[88;5u  :!echo B<CR>
noremap  <ESC>[49;5u  :!echo C<CR>
noremap  <ESC>[1;5P   :!echo D<CR>

The 5th line is very important: Ctrl-i, used to move back in the jump list, is not Tab anymore in Xterm; instead it sends a different sequence to Vim, thus that sequence should be mapped to what Vim has under Ctrl-i.

Extra notes

  • If you notice a delay when Esc is pressed in insert mode, adjust Vim's timeout settings, e.g. set timeoutlen=1000 ttimeoutlen=20 (see timeoutlen vs ttimeoutlen).

  • If in doubt what keysym should go in .Xresources, use xev to find it out. For example, pressing the left Windows/Super key outputs Super_L.

  • In Xterm, Ctrl-Q and Ctrl-S are reserved for flow control, a legacy feature. To map them, first deactivate flow control by adding

    " Disable XOFF/XON
    silent !stty -ixon
    " Redraw screen
    silent !resize>/dev/null

    to .vimrc.

  • To make the maps invisible to other TUI programs, you can keep Vim under a different Xterm classname, such as

    xterm -name vimterm -e vim file

    and use vimterm instead of XTerm in the .Xresources file. How to open new files in a same Vim instance may prove helpful.

Other terminal emulators: Urxvt and Kitty

Urxvt uses a different syntax in .Xresources. A interfering binding caused by ISO 14755 also has to be disabled.

URxvt*iso14755:    false
URxvt*keysym.C-i:  \033[105;5u
URxvt*keysym.C-X:  \033[88;5u
URxvt*keysym.C-1:  \033[49;5u
URxvt*keysym.C-F1: \033[1;5P

Kitty does not use .Xresources, the bindings go in ~/.config/kitty/kitty.conf:

map ctrl+shift+x send_text application \033[88;5u
map ctrl+i       send_text application \033[105;5u
map ctrl+1       send_text application \033[49;5u
map ctrl+F1      send_text application \033[1;5P
  • 1
    note that xrdb ~/.Xresources does a full replacement by default, so you will lose anything defined in /etc -- you may want to add the -merge option
    – graywh
    Commented Feb 1, 2021 at 19:56
  • @graywh The downside of -merge is that it will also preserve now-removed resources, potentially confusing some users when performing tests. Not all X sessions load the /etc/X11/... resources—mine does not—, so I went for no -merge. Thank you for the useful comment.
    – Quasímodo
    Commented Feb 2, 2021 at 11:59
  • I forgot about -override -- that's probably what I've used in the past
    – graywh
    Commented Feb 5, 2021 at 22:07
  • Hey! In your first example you say that we have to map Ctrl-Shift-x to CSI 88;5 u. Shouldn't the modifier value be 6 instead of 5?
    – Alex R
    Commented May 22, 2023 at 10:39
  • 1
    @AlexR, this bit is indeed a bit confusing, but no: 88 is uppercase X. You could use CSI 120;6 u though (120 is lowercase x). But in the end it doesn't really matter.
    – Quasímodo
    Commented May 22, 2023 at 17:30

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .