Message-ID: <5029C965.7030500@cs.utoronto.ca>
Date: Mon, 13 Aug 2012 23:43:33 -0400
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Strange "mouse" behavior in mintty
References: <50290217.6050202@cs.utoronto.ca> <5029B237.7010501@gmx.de>
In-Reply-To: <5029B237.7010501@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 13/08/2012 10:04 PM, Herbert Stocker wrote:
> Hi Ryan,
>
> On 13.08.2012 15:33, Ryan Johnson wrote:
>> Hi all,
>>
>> I'm hitting  a mouse-related (?) problem with mintty in non-mouse mode.
>>
>> STC A: Log into a remote machine, invoke `sleep 10', and -- during 
>> the wait --- click anywhere on the line containing the cursor.
>>
>> STC B: Open tinyirc and click anywhere on the text entry line at the 
>> bottom
>>
>> Both cases will insert a long string like this: 
>> ^[[C^[[C^[[C^[[C^[[C^[[C^[[C^[[C^[[C^[[C^[[C^[[C^[[C (only about 4x 
>> longer)
> Did you notice that when you click somewhere in the command line, the 
> cursor moves
> to that position? i think it has to do with that.
>
> Go to the options dialog, select "Mouse" and uncheck "Clicks place 
> command line cursor".
> The effect should go away.
Yes, that's the feature I was saying is probably related (see quote 
below). I don't want to disable it because it's immensely useful... I 
just don't want it dumping a mountain of ^[[C escapes at odd times.

Poking around in terminfo docs says CSI C is a "non-destructive move 
right" ("cuf1" in terminfo parlance). Sounds like exactly the right 
thing to send, but I guess shells (or curses apps) that don't correctly 
handle cuf1 would give this behavior... though I'm surprised that 
cygwin's bash can handle it and linux can't, especially when it works 
during normal line editing. Or maybe it's ssh... my sshd won't run right 
now so I can't test that hypothesis.

Ryan


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple