This is the mail archive of the
cygwin-patches@sources.redhat.com
mailing list for the Cygwin project.
Re: Mouse support
- To: "'cygwin-patches at cygwin dot com'" <cygwin-patches at cygwin dot com>
- Subject: Re: Mouse support
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Fri, 1 Dec 2000 23:54:39 -0500
- References: <F10D23B02E54D011A0AB0020AF9CEFE988FA6E@lynx.ceddec.com>
- Reply-To: cygwin-patches at cygwin dot com
On Thu, Nov 30, 2000 at 04:35:08PM -0500, Town, Brad wrote:
>Attached are patches that enable xterm-style mouse event reporting for
>console windows.
>
>To use mouse event reporting, make sure your console windows do not have
>QuickEdit mode enabled.
>
>To enable ncurses support for the mouse, add "kmous=\E[M" to your source
>terminfo file and re-tic. I've tested it with ncurses's main test program
>"ncurses" and "knights" (an ncurses test program) as supplied by the Cygwin
>ncurses distribution.
>
>Issues:
>. Instead of mouse support always being enabled (as it is now), it should be
>enabled when the console receives \E[?1000h and disabled when the console
>receives \E[?1000l. (That's a lower-case 'L'.)
I think this is a big issue, actually.
I'd rather not enable this by default because people will be clicking in the
console window and will see strange characters in their bash shells, won't
they?
>. Single-clicking and triple-clicking seem to work fine, but for ncurses's
>"ncurses" program to see a double-click, you need to move the mouse
>afterward. I spent the better part of the afternoon looking for the cause,
>but to no avail.
Hmm. Is select not returning correctly, maybe?
cgf