Re: mouse support in the Info reader (was: newer info reader does not allow text selection per mouse)

[Eli Zaretskii]

> Date: Mon, 6 Apr 2015 15:40:44 +0100
> From: Gavin Smith <address@hidden>
> Cc: Texinfo <address@hidden>
> 
> On 6 April 2015 at 15:19, Eli Zaretskii <address@hidden> wrote:
> >> Date: Mon, 6 Apr 2015 15:03:43 +0100
> >> From: Gavin Smith <address@hidden>
> >> Cc: Texinfo <address@hidden>
> >>
> >> My only thought is that the value of the "mouse" variable will be
> >> misleading, because the mouse events will be being captured by a
> >> different method to that under xterm. Perhaps we could have an extra
> >> value for this variable which it would default to under MS-Windows. I
> >> don't care much about this though, so don't worry if it would be too
> >> much effort.
> >
> > Maybe I missed something: why does the exact method of capturing
> > matter on the user level?
> 
> 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.