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: Sat, 04 Feb 2017 16:13:00 -0000	[thread overview]
Message-ID: <87vasqrl2a.fsf@Rainer.invalid> (raw)
In-Reply-To: <announce.245a59b4-c8dd-31c0-8f79-3b1c8e28a139@towo.net> (Thomas	Wolff's message of "Fri, 27 Jan 2017 22:17:16 +0100")

Thomas Wolff writes:
> I have uploaded mintty 2.7.4 with the following changes:

Since about November/December last year I'm having problems with screen
and tmux sessions in mintty not correctly refreshing and leaving garbage
characters displayed in the terminal.  It seems that the terminal size
is not always correctly reported, especially if you make the window
occupy the left or right half of the screen via Windows shortcut.

Additionally, there seems to be an off-by-one bug when the last line of
the terminal needs to be scrolled up in order to show content that is
longer than the remaining width.  This happens when you for instance
recall a long command from history.  It's hard to see what exactoly
happens, but it looks like the one character too many gets printed (and
wraps onto the next line) before the whole terminal window gest scrolled
up and the rest of the command gets printed in the line below the
single wrapped character.  That remainder is in various states of
disarray, showing both remnants from the original prompt on the last
line (now three lines up), empty /spaces where there should have been
characters from the command and then of course parts of the command.

I'm not seeing these problems when I'm working via konsole from a
Linux box.


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

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

--
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-04 16:13 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 [this message]
2017-02-05 18:36   ` Thomas Wolff
2017-02-05 18:55     ` Achim Gratz
2017-02-06 19:16       ` Achim Gratz
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=87vasqrl2a.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).