Mintty text glitches when using up key

Brian Inglis Brian.Inglis@SystematicSw.ab.ca
Thu Aug 27 19:55:59 GMT 2020


On 2020-08-27 10:55, Hamish McIntyre-Bhatty via Cygwin wrote:
> 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.

Not a problem with long lines - often find myself editing a few lines down in a
few hundred characters long after some iterations - I type without thought:

	$ history | tail > ~/bin/script
	$ vim + !$

Problem is when you type ahead too fast, hit modifier keys and/or special
functions by mistake in the wrong place, and/or when something else is running
in the background, or the system is loaded, and mintty does not grab the whole
escape sequence to process; often just running reset will restore sanity.

[For real fun with mintty, type: $ echo `/usr/bin/env /usr/bin/python`
You can kill python from another terminal window or TaskMgr.]

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]


More information about the Cygwin mailing list