> Date: Tue, 7 Apr 2015 11:29:19 +0100 > From: Gavin Smith <[email protected]> > Cc: Texinfo <[email protected]> > > On 6 April 2015 at 15:54, Eli Zaretskii <[email protected]> wrote: > >> It might matter if one method works better than another, or the user > >> might just be curious. I was mainly thinking that this variable might > >> have other options in the future, such as other terminal modes (there > >> are several that can read mouse events) or getting events from the gpm > >> daemon. > > > > Ah, okay. Then I think those other options should not be available on > > Windows, as there's only the "normal-tracking" method there. OTOH, > > having a Windows-only value would mean users cannot have > > platform-independent init files and/or muscle memory. > > Maybe it is obvious, but it is not clear from your reply that you > realise that "normal tracking mode" is not used under Windows. By this > I mean specifically the terminal mode entered with the "ESC [ ? 1000 > h" sequence. (reference > http://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h2-Mouse-Tracking).
I interpreted "normal-tracking" as the method available by default. I didn't realize that it refers to something xterm-specific. I don't see this term in the xterm page you refer to. > One idea is to have an "automatic" option for the "mouse" variable > that would use whatever method was available. But I am happy enough > with the way it works at present, as I said. Having values specific to certain terminals might make sense if there are terminals that support more than one value. In that case, I think we do need some default value, perhaps just "On" on the user level. In any case, I think we can defer the decision to a later date. Thanks.
