2012-10-02 "Benjamin R. Haskell" <[email protected]>:
Hi Benjamin > When I've found sequences like this that don't have termcap/terminfo > (historical) counterparts, I've tried to do what XTerm's > "modifyOtherKeys" mode does. It uses CSI Ps[;Ps[;Ps]] ~ to provide a > more extensible set of key codes. (And, for better or worse, since it's > XTerm, it may well become a de facto standard.) > > In the case of Ctrl+Tab, it produces (spaces added): > > CSI 27 ; 5 ; 9 ~ > 27 = extended key (...I think) > 5 = Ctrl ( 2 = Shift ; 6 = Ctrl+Shift ; etc. ) > 9 = ASCII code for Tab > > So, you can add to your .Xresources/.Xdefaults: > > URxvt.keysym.C-0xFF09: \033[27;5;9~ I added that line to my .Xresources and launched xrdb -merge .Xresources > (0xFF09 = keycode for Tab according to `xev` -- is there a simpler way? > "C-Tab" didn't work.) > > And add to your .vimrc: > > map <Esc>[27;5;9~ <C-Tab> I added the line and tried to create a mapping using <C-Tab>, but unfortunately it didn't work. To avoid any interference I started vim with -i NONE -u NONE and created a direct mapping: map <Esc>[27;5;9~ ifoo This also didn't work. It seems like ctrl-tab is interpreted as a simple tab character. Did this work for you? Can I somehow verify that the keysym was successful? Thanks a lot for your instructions. Marco _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
