From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: Cygwin General Mailing List <cygwin@cygwin.com>
Subject: Mintty text glitches when using up key
Date: Thu, 27 Aug 2020 17:55:13 +0100 [thread overview]
Message-ID: <DB7PR02MB3996E72ECDDB5C0A9F2F8D3AE7550@DB7PR02MB3996.eurprd02.prod.outlook.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 906 bytes --]
Hi,
For a while I've noticed that if I run a long command (usually has to
wrap to next line down), that my Mintty session often becomes all messed
up if I use the up arrow keys to try and run it again later. Has anyone
else experienced this?
Another, probably unrelated, observation is that if a command produces a
lot of long lines that get wrapped, if I make the Mintty window wider,
the lines stay wrapped. This behaves much like other terminal emulators
I used in the past, including gnome-terminal. At some point, this was
fixed in gnome-terminal, so I wonder if that fix would be relevant here too.
Unfortunately I know precious little about how terminal emulation works
so I'm not likely to be able to provide a fix, but I'm interested to see
if anyone else has experienced this or has found workarounds. It seems
to happen with both 32-bit and 64-bit Cygwin for me.
Hamish
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-08-27 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 16:55 Hamish McIntyre-Bhatty [this message]
2020-08-27 19:55 ` Brian Inglis
2020-08-28 8:33 ` Thomas Wolff
2020-08-28 14:31 ` Hamish McIntyre-Bhatty
2020-08-28 15:13 ` Thomas Wolff
2020-08-28 15:48 ` Hamish McIntyre-Bhatty
2020-08-28 16:45 ` Thomas Wolff
2020-09-02 15:28 ` Hamish McIntyre-Bhatty
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=DB7PR02MB3996E72ECDDB5C0A9F2F8D3AE7550@DB7PR02MB3996.eurprd02.prod.outlook.com \
--to=hamishmb@live.co.uk \
--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).