DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type:content-transfer-encoding;
	 q=dns; s=default; b=ML4ZMfgL1HIlsF6l2THku1RrLbUZM9Qq6mMH4AC1k4o
	WyVDX3kafqY6/5s5CpB3Hy/cv5Y32OhKJ48v8PHcuUJiO6pdZs/qhMNenSTfR7R2
	96H2O1tPJ4feA7XzrKnDI3sqF3ks8FTvbBd80dZSDEf/4U2N/CgoqfVvus11Z/aw
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.7.4
References: <announce.245a59b4-c8dd-31c0-8f79-3b1c8e28a139@towo.net>	<87vasqrl2a.fsf@Rainer.invalid>	<c377cada-562c-9a5d-14c3-b1f0b204abd5@towo.net>	<87mve0lb7e.fsf@Rainer.invalid>
Date: Mon, 06 Feb 2017 20:16:01 +0100
In-Reply-To: <87mve0lb7e.fsf@Rainer.invalid> (Achim Gratz's message of "Sun,	05 Feb 2017 19:55:01 +0100")
Message-ID: <87fujrgmfi.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.91 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

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.

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


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

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