Hi, first of all, http://software.schmorp.de/pkg/rxvt-unicode.html links to http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.7.html which seems to be obsolete, as it doesn't mention the 1015 mode.
I've tested three different terminals (all on Debian testing and X.org, though I don't expect any differences in newer dev versions). The following are results from me clicking the fwd. mouse button, followed by the back button: - xterm: DEC 1000, 1006: ^[[<3;1;1M^[[<3;1;1M^[[<3;1;1M^[[<3;1;1M - rxvt-unicode: DEC 1000, 1015: ^[[101;1;1M^[[100;1;1M - suckless terminal: DEC 1000, 1006: ^[[<69;1;1M^[[<69;1;1m^[[<68;1;1M^[[<68;1;1m Only stterm is even acceptable! Interestingly, urxvt and stterm agree on codes 69 and 68, after normalisation. Given that the general mouse button sequence in X11 seems to be: 1 = left button 2 = middle button (pressing the scroll wheel) 3 = right button 4 = turn scroll wheel up 5 = turn scroll wheel down 6 = push scroll wheel left 7 = push scroll wheel right 8 = 4th button (aka browser backward button) 9 = 5th button (aka browser forward button) it should be safe to treat 8 and 9 as clickable buttons, and perhaps 6 and 7 as well, though I don't have such a mouse and can't tell you whether X.org may produce a ButtonRelease event with a different timestamp. Thus, rxvt-unicode should, given its preferred way of letting the application know that a mouse button has been depressed, follow its 101 and 100 sequences with ^[[35;1;1M upon ButtonRelease. I've already mailed Dickey, maybe we can fix this. Thanks, Přemysl Janouch _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/mailman/listinfo/rxvt-unicode
