rxvt-unicode's strange handling of function keys (with modifiers)

Hello, urxvt/rxvt-unicode has a strange method of handling function keys. It defines kf1=\E[11~ to kf20=\E[34~ in its terminfo, but only has a concept of 10 function keys (kf1 to kf10), and then uses kf11 to kf20 for the shifted variants. For F11/F12 it sends the same code as for Shift-F1/F2. I

terminal-overrides for rxvt-unicode

Hello, I've been using urxvt/rxvt-unicode with TERM=xterm-256color for a while, but now switched back to its default (TERM=rxvt-unicode-256color). But the defaults for "terminal-overrides" in tmux only consider xterm*: ",xterm*:XT:Ms=\\E]52;%p1%s;%p2%s\\007" ":Cs=\\E]12;%p1%s\\007:Cr=\\E

[PATCH] Fix xterm-keys.vim example: t_kP/t_kN defined wrong

From: Daniel Hahler It should not be necessary to define them, since PageUp/PageDown is alread, and it should be the same. But the way it was defined actually broke PageUp/PageDown, because '\e' or a real escape should have been used. --- examples/xterm-keys.vim | 3 --- 1 file changed, 3 delet