public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.7.4
Date: Mon, 06 Feb 2017 19:16:00 -0000	[thread overview]
Message-ID: <87fujrgmfi.fsf@Rainer.invalid> (raw)
In-Reply-To: <87mve0lb7e.fsf@Rainer.invalid> (Achim Gratz's message of "Sun,	05 Feb 2017 19:55:01 +0100")

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

  reply	other threads:[~2017-02-06 19:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 21:45 Thomas Wolff
2017-02-04 16:13 ` Achim Gratz
2017-02-05 18:36   ` Thomas Wolff
2017-02-05 18:55     ` Achim Gratz
2017-02-06 19:16       ` Achim Gratz [this message]
2017-02-06 19:29         ` Thomas Wolff
2017-02-05 20:36     ` Brian Inglis
2017-02-06 19:46       ` Thomas Wolff
2017-02-07  1:03         ` Doug Henderson
2017-02-07  7:31         ` Brian Inglis
2017-02-07 20:52           ` Thomas Wolff
2017-02-08  2:17             ` Brian Inglis
2017-02-08 18:35             ` Achim Gratz
2017-02-08 22:52               ` Thomas Wolff
2017-02-09 19:37                 ` Thomas Wolff
2017-02-09 19:42                   ` Achim Gratz
2017-02-09 20:09                     ` Thomas Wolff
2017-02-07 21:00           ` diagnostic character info (Re: [ANNOUNCEMENT] Updated: mintty 2.7.4) Thomas Wolff
2017-02-09 19:38             ` Thomas Wolff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fujrgmfi.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).