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=rydbtViQrXBUsGhD
	0CC2MtnFm4i32z47El2chasOJUHot35mh+QAVXyQIqdOf5krqbkYhds7ZsaqfYsw
	mSH+qZ+TQ/nRfMAuJM3FIVGep2L+FkEeeRQX9yDXvPRo34b/IugNueePzeDr6dt2
	7/bhRrknpmZnwv4kp2idDQ+F9so=
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=jiZDcL2QUr3DWj+VMbDwry
	WskwI=; b=fCal/N8wSCAW/FG7yhH4L0bjVUhgX1GUNkW88cXZZop+CzRpb/MNso
	SDEi9wCpXa4vaXiZRXqb5/0C85Q95ZAq4QdBEJIBrbo650VYCFLyL+ygQ7x2LkWo
	M8RF/ui71eURwIlc3dWPK+rNnTlsyHSxJgxcsbJbSM3zN5y2r6piY=
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.0 required=5.0 tests=AWL,BAYES_00,FOREIGN_BODY,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=wurde, wwwavastcom, UD:www.avast.com, www.avast.com
X-HELO: mout.kundenserver.de
Subject: 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> <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> <87o9fohy8a DOT fsf AT Rainer DOT invalid>
From: Thomas Wolff <towo AT towo DOT net>
Message-ID: <897e8e8b-e884-d0d7-f0a1-3256480a13dd@towo.net>
Date: Wed, 4 Jul 2018 07:27:06 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <87o9fohy8a.fsf@Rainer.invalid>
Content-Type: text/plain; charset=utf-8; format=flowed
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id w645RN5X016266

Am 03.07.2018 um 22:15 schrieb Achim Gratz:
> Thomas Wolff writes:
>> 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 need to set this in a script that starts up a bunch of mosh sessions
> across my servers at work.  I nest screen (on the remote side) into tmux
> (local side), mostly in order to be sure the escape keys are different.
> One day I might move to nested tmux sessions once I figure out how to
> reliably switch to a different escape in the second level tmux.
Andrey quoted how he configures 'screen'; can you show the relevant part
of 'tmux' configuration please?

>> Such issues could also be discussed in the mintty chat
>> https://github.com/mintty/mintty/issues/777
> Since github requires an account for that I will have to decline.
I see the point.

>> As mintty has always used a configured log file name (unlike xterm
>> using a fixed pattern), the absence of one would be a design problem.
> THe idea was that if no file name was configured (or the wrong one), you
> could set one from the extended config dialog so that it is then
> possible to enable logging.
Wasn't sure but got the idea now; however, this will not work as the
menu implementation only allows to select an item, not to interact. It
could only go into the Options dialog, then. Not sure whether that's
desirable, considering that the Options dialog has always been kept
small, still by Andy's design approach.

>> I know I raised the idea, but having thought again, this could imply
>> that a lot of settings might be markable as "fixed",
>> including all mode settings, character set settings, and others, to
>> avoid accidentally confused settings for one or the other person.
>> I'm hesitating to take a step into such a direction.
> Well, a more sustainable strategy would perhaps be to make the supported
> feature set configurable, maybe like sort of a theme file.  That file
> might even become self-documenting.
What I see feasible is one additional config parameter, not a new
mechanism. Maybe only covering DECSET features, with something like
'BlockModes=34,47,1047,...'.

Thomas

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


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