This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: mintty 2.7.4
- From: Thomas Wolff <towo at towo dot net>
- To: cygwin at cygwin dot com
- Date: Mon, 6 Feb 2017 20:28:55 +0100
- Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.7.4
- Authentication-results: sourceware.org; auth=none
- References: <firstname.lastname@example.org> <87vasqrl2a.fsf@Rainer.invalid> <email@example.com> <87mve0lb7e.fsf@Rainer.invalid> <87fujrgmfi.fsf@Rainer.invalid>
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.
See above. This might have helped already but it didn't. More precise
reproduction instructions are needed.
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
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple