After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 736447 - Mouse mode 1003 is unlike xterm
Mouse mode 1003 is unlike xterm
Status: RESOLVED OBSOLETE
Product: vte
Classification: Core
Component: general
0.37.x
Other Linux
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-09-11 00:02 UTC by Egmont Koblinger
Modified: 2021-06-10 14:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Egmont Koblinger 2014-09-11 00:02:07 UTC 
vte says:
1002: Cell motion tracking.
1003: All motion tracking.

xterm says:
#define SET_BTN_EVENT_MOUSE         1002
#define SET_ANY_EVENT_MOUSE         1003

1002 is the same in vte and xterm.

In xterm, 1003 is different from 1002 so that movement is reported even if no button is pressed - but it's still only reported if the mouse is moved to another cell.

In vte, 1003 reports movement even if no button is pressed, moreover, even if the mouse stays in the current cell (it reports the same coordinates again). So it's different from 1002 in two aspects.

Some terminals, e.g. konsole reports movements within the same cell, but then it does it for both 1002 and 1003.

So apparently the intended difference between 1002 and 1003 is _not_ cell motion vs. all motion, it is whether to report movement if no button is pressed.

ctlseqs.txt says
Ps = 1 0 0 2  -> Use Cell Motion Mouse Tracking.
Ps = 1 0 0 3  -> Use All Motion Mouse Tracking.
which seems to be buggy. (Or is xterm broken??)
Comment 1 Egmont Koblinger 2015-02-24 09:59:41 UTC 
See also bug 745074.
Comment 2 GNOME Infrastructure Team 2021-06-10 14:56:02 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/vte/-/issues/2133.