X-Recipient: archive-cygwin@delorie.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=QBxNYeDQY3RbMFgj
	PCQzxDj8raWYOyap9u3FwLElIeSFnxSQjVAS0KdCpy9t6sB9eMjtqD6hmoSOn+ya
	9ioQp90jGIA1yrvkXBE4TncvWc0TJxiIigEK6lq+PaGC+Fr5arPbQAIHijI7M9wB
	kwbTmY+VtOx6YfL/aTCxpOc0NnM=
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=XzaBoAvEvi9kaKfGU8F+/S
	bDU0Q=; b=RRH4knjufM3dXUpLKKyqYJR8jgj2XT5abqTkzWByBgYdSdZR6hbbf2
	78SsLfMcetXeTyVP8kpmemT/u5PdXfscHzyBcFShxungXXBVXocg9yLunIcRYS2O
	OApBVp1e2eTgo31xuW7cLuPb+8mf0KWdHultIGb/UXTSobTOBSIag=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=colors, Gratz, gratz, Greetings
X-HELO: mout.kundenserver.de
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.0
To: cygwin@cygwin.com
References: <announce.f1fa99f9-4d45-8314-50ed-ac95b79dd43d@towo.net> <87zhz9bcyt.fsf@Rainer.invalid> <99897D710406F142A5DE486B0F3B7BC101461E7DBB@EMP-EXMR203.corp.leidos.com> <09aedfda-f35b-5c33-6bef-cef52c9f041c@towo.net> <87va9wi4pb.fsf@Rainer.invalid> <9e3c9045-4d02-cd66-dae1-8558cdf2a14f@towo.net> <519069560.20180704024051@yandex.ru>
From: Thomas Wolff <towo@towo.net>
Message-ID: <78570129-7850-f9b7-4438-38b5b40357c8@towo.net>
Date: Wed, 4 Jul 2018 08:40:09 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <519069560.20180704024051@yandex.ru>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes
Note-from-DJ: This may be spam

Am 04.07.2018 um 01:40 schrieb Andrey Repin:
> Greetings, Thomas Wolff!
>
>> Am 03.07.2018 um 19:56 schrieb Achim Gratz:
>>> Thomas Wolff writes:
>>>> ... the assumption is that tmux sends it on purpose, so
>>>> the blame is on tmux :/
>>> Not tmux, what you need to blame is the terminfo entry for
>>> screen-256color again, specifically the cursor_normal variable.  There
>>> are a bunch of other terminals using the same sequences though.  But I
>>> need to set the terminal to this exact string or colors inside screen
>>> (e.g. Emacs) don't work correctly (it falls back to some lower number of
>>> colors and gets completely illegible with the default theme).  Anyway,
>>> since I already needed to patch the stupid italics/bold swap in that
>>> terminfo entry, I just patched out this bit of nonsense as well.
>> As I cannot reproduce the exact scenario, I don't see yet where/how you
>> set TERM=screen-256color and when the cursor would switch.
>> Also I notice that the xterm-256color entry is missing the Co entry
>> (which is likely what you want), strange.
> I have this stuff in my .screenrc
>
> term "screen-256color"
> termcapinfo *-256color* 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
> defbce on
> altscreen on
Although I see the 34 mode in terminfo, I still cannot reproduce the 
cursor switching behaviour,
neither with this .screenrc, nor with a .tmux.conf with 'set-option 
default-terminal screen-256color'.
According to TERM=screen-256color infocmp -1|grep 34
         cnorm=\E[34h\E[?25h,
         cvvis=\E[34l,
the cursor could be turned into an underline when "cursor_normal" mode 
is restored, i.e. when a screen application terminates.
But which application does actually send the cnorm sequence?
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

