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=gyH36LCDACIh0ZbL
	wXajo8PixLA/+SFv1XfYygVnug8X/P9lrxoqUHEuzgDKE/6K5okk1+b92he5kx3R
	yNaxG1jYmyyr9Mw5QSWDsLyu7TgmqsC8AODTeM64G27FtK6uJ/6jys5MY1bDuXQ7
	TXvj4FvNVHcw9ORxLf3R9qXUJmQ=
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=ZIyz5Ubejx3FaElSoQszLu
	iGuQI=; b=hD5iZGTqQmtF86Yl8DosMRfyiyu2flnJUYOiTwNAuI3M0E9iCL3fvP
	XRyAThcWOhFmgAd9e88BJyf2UBwIPpJmH6RBBEU9v7tlllrAnd18zm1pjFJJJsV5
	IPR8aoDITkcN8jMnP2WPkXIf4ZBys/fN0boFrlFQbVRQeDqJjiyoA=
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.5 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=reproduction, remotely, 06022017, 06.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> <87mve0lb7e DOT fsf AT Rainer DOT invalid> <87fujrgmfi DOT fsf AT Rainer DOT invalid>
From:	Thomas Wolff <towo AT towo DOT net>
Message-ID:	<c1e17eb5-dd90-470c-5714-7c798dc6d678@towo.net>
Date:	Mon, 6 Feb 2017 20:28:55 +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:	<87fujrgmfi.fsf@Rainer.invalid>
X-UI-Out-Filterresults:	notjunk:1;V01:K0:MMJa5z75oFQ=:w5MV8l8WXscaAb3TyU0c83 OL5WOSgVSHFtB5ql+aggkTN0yvaXCekNS4q1Y7a1ix4rw8qgbVOXYyqO8KB8ktMt17pyELa7/ zFLB7a8YkZJxBqCd/vXHmWLi9KdDjlSmati4TZ/xPExr8u11j/8B1O9qaquwkCcIhgmaSQ4Y8 guYdEL+oHxb7ARDQeaOLALvcU7h5NO8hzLld2EkPwDL6SOZWSREVwCU1FUJmHZ806AIFtS0Lc 893HvBc5eMP9olIfQD1U4lzfA20xbDRjLCFBQJebm8hqYBtiUnM/TZmTBhMdc+ZfI+zxprQ/x PnWsxo2dRVGrhohF1dW9OTFDw/DMR8+R9hohgGZb+K5Lm2bzic4DfRGHga13FT3UzmqxNhbia cXXhhVTcCuz2vGGyegrIsKcR/K3ck/a7R4aZP00dpPnYWWnpGyX7yWxonMcVoGfDtTyKh+6Ur K0+j8LkLBY1CunfGJwRAPJb+xWDHNwt96MAr6rkr+c+uO4QkHuMhjkAzipWumQf1W8S0rjU8w 3ljoDnSLJaqNXo5/I3HJFVzCveVB9emw+FuJig9aG7BpmS/lqARnXJf0nbCSOyUwhJ7lDObal hHbiLXO7tFoO+p0FAa6mzuJnQ3Sq4HbZZXzIsFj5iEEvdftGQQ59DZRPNYu7Vu65QmrAeh9Ex wJhPbevjuxYIhxKeh+0pCK/1KAOSoUOTktm4zJ4cjCduABIzrNfoztWHVBmrv8qcXWW8PcW5Z VLY0iGozw5Cb8nF+
X-IsSubscribed:	yes

Am 06.02.2017 um 20:16 schrieb Achim Gratz:
> Achim Gratz writes:
>> Thomas Wolff writes:
>>> Is this within tmux or after leaving tmux (see comment below)? It
>>> would be help to cross-test this; if it's mintty, which version would
>>> show the behaviour first? What happens in xterm?
>> Within tmux or more often screen within tmux.  I'll have to try what
>> happens in plain mintty.
> OK, it's moreā€¦ interesting than I first thought.  I can reproduce it
> when setting up a screen session inside tmux and I might need to be
> connected to the screen session via mosh.  It doesn't consistently
> happen even then.  I first thought it had something to do with my
> setting TERM to xterm-256color, but it happens with screen-256color as
> well.  I've had the issue appear when switching the TERM variable to
> xterm-256color and it didn't go away when I've reverted to
> screen-256color.  I've meanwhile confirmed I get the same problem when
> I'm running under screen-256color all the way from the first shell.
Why would you want to run screen within tmux?
Anyway, I cannot reproduce the issue, although I used to have strange 
effects with a remote screen or tmux once myself.
I'd either need a reproducible test case (like start a fresh mintty, run 
screen (locally/remotely?), type a certain command etc),
or, likely easier in this case, a screen log that demonstrates the 
effect (mintty -l logfile).
You may also try to toggle wraparound mode; see the mail I'm going to 
write in response to Brian's response.

>> No, I don't think it's related to that issue and I haven't changed my
>> prompt in years.  It's specifically happening only on the last line in
>> the terminal window with the first character that should wrap onto the
>> next line and not anywhere else and only when scrolling the window
>> happens.  If the shell has lost the correct terminal geometry, then it's
>> wrong on all lines of the terminal, not just the last in my experience.
> I can actually provoke this by simply typing in a too long line: when
> the last character in the last line gets entered, the terminal opens a
> new line below, scrolling the content up one line (and keeping the
> status line of the tmux in place on the _real_ last line).  It then
> scrolls up another line, repeats the the first character of the prompt
> on the original line and appends any further characters entered after
> that character.
See above. This might have helped already but it didn't. More precise 
reproduction instructions are needed.
------
Kind regards
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 -