Hello, I just discovered the vt100.translations resource as I wanted to use the wheel in mutt (which does NOT support it) The xterm trick is to "bind" (?) the button to a string that mutt can then interpret. The following works with xterm :
mutt_resource.vt100.translations: #override \n\ Mod4 <Btn4Down>,<Btn4Up>: string(<<) \n\ Mod4 <Btn5Down>,<Btn5Up>: string(>>) \n (with a muttrc containing :) bind pager < previous-line bind pager > next-line bind index < previous-undeleted bind index > next-undeleted But ... in urxvt it doesn't work and I my attempts to diff the terminfo with infocmp and listres failed to give me the begining of an explanation. In the theory I know it's up to mutt to handle the mouse and the mouse doesn't seem to be part of the keysyms of the Xresources, anyway urxvt has the mouseWheelScrollPage resource so I still think that the wheel is somewhere internally ""handled"". Does someone have already dig this ""issue"" ? Raph _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
