2012-10-02 "Benjamin R. Haskell" <[email protected]>:
> > This also didn't work. It seems like ctrl-tab is interpreted as a > > simple tab character. Did this work for you? > > Yes, it worked for me. > > As mentioned, the 0xFF09 in .Xresources seemed odd to me. You might try > looking at the output of `xev` (X11 Event Tester) to see the correct > code for your machine. On my current laptop (under X.Org X Server > 1.12.1), hitting Ctrl+Tab, I get (among many other things): > > KeyPress event, serial 33, synthetic NO, window 0x3e00001, > root 0x166, subw 0x0, time 93314998, (88,71), root:(89,94), > state 0x10, keycode 23 (keysym 0xff09, Tab), same_screen YES, > XLookupString gives 1 bytes: (09) "" > XmbLookupString gives 1 bytes: (09) "" > XFilterEvent returns: False The keysym is 0xff09 on my system as well. > Possibly, also, just try the version I'd expect would work (since XK_Tab > is the name for the keysym): > > URxvt.keysym.C-Tab: \033[27;5;9~ This works, as well as URxvt.keysym.0xff09 does. It was my fault. I was fooled by the xrdb -query output, which listed the new value, but of course only in new started terminals, not in the current one. > Maybe something on my system prevents that from working right. > > > > Can I somehow verify that the keysym was successful? Thanks a lot for > > your instructions. > > For just testing that the .keysym. resource "takes", I've been running: > > cat -v In a fresh terminal this reports the correct key sequences. Thanks a million for the help. I now can map <C-Tab> in vim. However, it behaves wrong. Pressing <C-Tab> in insert mode capitalises the last character and goes to normal mode for whatever reason. But that's an issue to figure out on the vim list, not here. Marc and Benjamin, thanks to both of you. Marco _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
