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=ep/fyNYfmUA/JHEV
	YFOzM7HZsbqmQEo6JyjPQs5rEtDh85teJRdblKquGWQTU91RIL2tzA3CHZYTKgkZ
	3vY+RbQHFYPrdxz2vfZspCbbh4QcglVX/Bq9+1iVLfjyBUlAVNn7j1iRGShEO9kW
	U3p17m/Tu5iEMHORjdh+2oKmjE4=
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=dxkXY2GQhaIKaP6MGapnyn
	JZmBc=; b=IDd9Saq87SbWUqagsmjsOGBCwgfzfsh6qQHxGzFPPxlL/nsMWIxNYw
	T9drBpyjTPVjCNut+NqmLkmyIyeSQK4GF6+763oyfH1LepK/vYF9Dulcvw4Xd9aH
	XiFHvxSyQcOo4KeVgQWTi1TzvLKxHIxQmGmmN9IJHjFAVDEq4I6rQ=
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-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.2 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM autolearn=no version=3.3.2 spammy=logfiles, 09022017, considerably, 09.02.2017
X-HELO:	mout.kundenserver.de
Subject:	Re: [ANNOUNCEMENT] Updated: mintty 2.7.4
To:	cygwin AT cygwin DOT com
References:	<announce DOT 245a59b4-c8dd-31c0-8f79-3b1c8e28a139 AT towo DOT net> <87vasqrl2a DOT fsf AT Rainer DOT invalid> <c377cada-562c-9a5d-14c3-b1f0b204abd5 AT towo DOT net> <25e79ef3-c0ca-2d9f-7353-413580222412 AT SystematicSw DOT ab DOT ca> <52fb66c3-5dc5-afd7-02bf-acdb0a2a9972 AT towo DOT net> <bba687bb-b724-a7d2-2608-3bdc3af772ff AT SystematicSw DOT ab DOT ca> <9c13d3fc-9dbd-f89f-05da-28525e0e16e0 AT towo DOT net> <87r3383515 DOT fsf AT Rainer DOT invalid> <3e775b3d-2a2a-4cd8-4168-4cc4d502da06 AT towo DOT net> <d02c301d-b8b4-3c63-00a1-e1c1f886a368 AT towo DOT net> <874m03cfsy DOT fsf AT Rainer DOT invalid>
From:	Thomas Wolff <towo AT towo DOT net>
Message-ID:	<0f7e2ff0-ea79-2c73-fde9-af9174f4a1a6@towo.net>
Date:	Thu, 9 Feb 2017 21:09:11 +0100
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version:	1.0
In-Reply-To:	<874m03cfsy.fsf@Rainer.invalid>
X-UI-Out-Filterresults:	notjunk:1;V01:K0:WSoJ8yrKPow=:Z2Diq717n1x9F6X0tSQX7x mmEU/KiOQgUXjqVruhDnIhP2gX48A4BZwss3ezSAdF+o4RGbMGUaxSFM0zv/dKaA7JzzCXLzk UINbijDEqk44zq9Md8tZUYNH3ODCyI+HdQMWFgxn5JAYTid+qCXgisfXC9Hu/O478EMN6RhWC NgIgeizCV/575ZbdpL4sMTwhp0IIPv3ibTZvzlxfVl6Q5ApcOHE8bhWy4oPcQzrWkW/3oxGYs lNB2G+uudmMMPXoJwmTe4ZNGM1/PlPnmX1PRB096x2r2+OXVwWVEshW0S6kNodbFbq5Ey9QtI 2japFvOpb2a4I2HuCyVyejkvW96z0YjORYOdvp2d+Vr4Fm9K0MA7a10a8++sBs77gO2CjwJmQ k3oEpDwb3AYinkpqOCJT57nLk1xn8i8d5WBXFtZvQ2VYgOouzcUcFRkdiod+zw7Y4u3Ic26eb wAUS++MtiwdRJr/hLE+oVyXxRHNP4qkKOyk1SGGBOrghnkqPlUv0EDJqSLSM0A8OX8ywnOkUR fcIAa5zyYu7RI4ME9PZSlRXaYh08Du0ashRpfHrXasWbRFvlKXIjt4r/bG3opdlSOTpXVqiHy p0WG6e8+CI2H5w2HgrasjXYddv3GOrM5ydanrIyLEGAKi2wN2i4bkOLJLuj6Trk53FLbnHpS4 dbRItWZJXrFaqnkcnvX7k8Up8noex5N4bkLViM78sy08enQJ3cFMmNYjQH6H7nw99qtma3CMl ynVgQVsTv/IBb/wb
X-IsSubscribed:	yes

Am 09.02.2017 um 20:41 schrieb Achim Gratz:
> Thomas Wolff writes:
>> The man page speaks about speculative local echo which sounds like
>> asking for trouble...
> It is indispensable when you have a long-latency link.
>
>> Anyway, I could reproduce effects as you described with
>> mintty – tmux – mosh localhost (no additional screen needed)
>> And, most interesting for me: the same thing happens in xterm, so it’s
>> not a mintty issue :)
> OK, so that saves me the bother of trying to reproduce it at home
> because you already have.  Do you maybe have a workaround, otherwise
> I'll have to check if a mosh or tmux update has triggered it.
Both mosh and tmux try to fiddle around the worries of wraparound mode 
with their own tricky handling, as can be seen by the escape sequences 
in the logfiles if I run only one of them at a time, tmux considerably 
more than mosh.
It's not surprising that this interferes with each other.
------
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 -