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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=p3N+lK2wqEaYigij 3ph+tJZOXE/qn3jnYCoTHMvs7ZLBdslqNWK1dRS1F7ZhGDYgX15hlafiBi0IcGt1 vLM1sdXD9ecWQbA7ogba5hRA5Gw5441VcHHCVFK9IFH0DpYhCznhowsrqmVva4jb aFZZYMc8z+fFFsnF0XCcNO+Dw8M= 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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=riVlvqUk0Nj7yoMwIUjyzK Xz2tE=; b=WonVk2xxfoZcJYlKV34io16uc9saXM5E/uIArjy1FKz0wutwNuXc1M 1BqjGbvgDSRs0mArUpBpOctsVUjobzcJPYXXjSCEw/bznt3qMvAIAB3eDVDrH1+/ WHF3E5pPedgZ6vDeebQmX92OKYl+yxWvG1GrbPY5+5Uww4ojOJ+Cc= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.3 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*R:D*ca X-HELO: smtp-out-so.shaw.ca Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.0 To: cygwin AT cygwin DOT com References: <87zhz9bcyt DOT fsf AT Rainer DOT invalid> <99897D710406F142A5DE486B0F3B7BC101461E7DBB AT EMP-EXMR203 DOT corp DOT leidos DOT com> <09aedfda-f35b-5c33-6bef-cef52c9f041c AT towo DOT net> <87va9wi4pb DOT fsf AT Rainer DOT invalid> <9e3c9045-4d02-cd66-dae1-8558cdf2a14f AT towo DOT net> <519069560 DOT 20180704024051 AT yandex DOT ru> <78570129-7850-f9b7-4438-38b5b40357c8 AT towo DOT net> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: <4f4869bc-2d9c-9858-1a0b-89bac41b81f5@SystematicSw.ab.ca> Date: Wed, 4 Jul 2018 13:08:31 -0600 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: <78570129-7850-f9b7-4438-38b5b40357c8@towo.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Note-from-DJ: This may be spam On 2018-07-04 00:40, Thomas Wolff wrote: > 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? It seems that the effects of a command could conflict with user preferences, and it is a design decision which alternative should apply, possibly annoying the user with unexpected results in either case. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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