X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=njme9zEN4MYvWis0
	dv32KzrL/GyYcxp1dGRqP9+8s8KjQwbwJKG8E/i3YjTl4t/iLE44WEKSpIrYkwCx
	U+HDnHGTHiEIVZLKl3x5oVo8F8eS9mllGk5nR6kELZGuDpCWU8yhB9iwhD/K0S/T
	8PZANsXb+6fp2DBf+OKoj4f3CD0=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=RYNRx5GR/ETuNqLdadtBpl
	vxPxw=; b=InUZWTAEAGpC5wLXnEQzFRscg8SyrNt7SzdHjmcYCAf9YeK5X7vv8k
	ssE/c7EMzb1kEikxtnPceKFZZLlr0H4UPKa/VP0+jlrJlJx/P9hZK2bDWxZNsb5j
	tBc9MqskW9k7w5U0yPxsGC50KYdEcW2195ZXcOWNeVPja4lMT3ysU=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=1.6 required=5.0 tests=AWL,BAYES_50,HTML_MESSAGE,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=session, Rogers, rogers, wells
X-HELO:	mout.kundenserver.de
Subject:	Re: Re: [ANNOUNCEMENT] Updated: mintty 2.9.0
To:	cygwin AT cygwin DOT com
References:	<announce DOT f1fa99f9-4d45-8314-50ed-ac95b79dd43d AT towo DOT net> <87zhz9bcyt DOT fsf AT Rainer DOT invalid> <99897D710406F142A5DE486B0F3B7BC101461E7DBB AT EMP-EXMR203 DOT corp DOT leidos DOT com>
From:	Thomas Wolff <towo AT towo DOT net>
Message-ID:	<09aedfda-f35b-5c33-6bef-cef52c9f041c@towo.net>
Date:	Tue, 3 Jul 2018 09:39:30 +0200
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version:	1.0
In-Reply-To:	<99897D710406F142A5DE486B0F3B7BC101461E7DBB@EMP-EXMR203.corp.leidos.com>
X-IsSubscribed:	yes

On 02.07.2018 23:39, Wells, Roger K. wrote:
> On 07/02/2018 04:27 PM, Achim Gratz wrote:
>> Thomas Wolff writes:
>>> I have uploaded mintty 2.9.0 with the following changes:
>> […]
>>
>> No good deed goes unpunished, I guess.  One of these changes makes the
>> cursor come out as static underline instead of blinking block whenever
>> I'm going into my usual screen or tmux session.  I have not yet figured
>> out what exactly is changing the cursor, but once I'm in screen nor tmux
>> I can't change it for whatever reason (it might actually change and gets
>> reset quickly enough so I can't see it).  Dropping out of the session I
>> can send the escape sequence to switch back to blinking block (or
>> whatever other cursor available), but reconnecting into the session
>> brings the static underline back.  The best I have managed so far by
>> compiling my own terminfo database is to get a static block cursor (not
>> blinking) for a local session, but it breaks down as soon as I log into
>> a remote system again.
>>
>> Can there be an option please to keep the cursor just as I've set it up
>> in the options?
>>
>>
>> Regards,
>> Achim.
> Hi,
> I just did the same install and do not observe what you do.
> Everything seems fine regarding the cursor type.
> One thing though is that I have not used mintty before.
> Do you think that my fresh ".minttyrc" file is different than your's?
> Just a thought......
I guess it's more about the configuration of tmux. There is in fact a 
cursor style setting sequence that mintty newly supports.
Please make a terminal log and check whether ^[[34h (ESC [ 3 4 h) 
appears during tmux initialization. If so, however, the assumption is 
that tmux sends it on purpose, so the blame is on tmux :/ My tmux 
configuration does not change the cursor, like Roger's, by the way.
About an option to suppress dynamic changes of cursor style, that might 
indeed be useful. I assume, though, that it should uniformly also 
suppress the DEC sequence (DECSCUSR). Or should different cursor 
attributes be addressable separately? (shape, blinking, colour??, even 
hiding???)
Design proposals welcome.
Thomas

--
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

- Raw text -