X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 270EA3857C62
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=towo.net
Authentication-Results: sourceware.org; spf=none smtp.mailfrom=towo AT towo DOT net
Subject: Re: Mintty text glitches when using up key
To: cygwin AT cygwin DOT com
References: <DB7PR02MB3996E72ECDDB5C0A9F2F8D3AE7550 AT DB7PR02MB3996 DOT eurprd02 DOT prod DOT outlook DOT com>
 <c064a9ce-ec21-ff87-29a2-c9f6a510b773 AT SystematicSw DOT ab DOT ca>
 <4214ab62-9f2c-0c9d-26f1-5fff8ec2c376 AT towo DOT net>
 <DB7PR02MB3996657CA16B0B48A6DE6114E7520 AT DB7PR02MB3996 DOT eurprd02 DOT prod DOT outlook DOT com>
From: Thomas Wolff <towo AT towo DOT net>
X-Tagtoolbar-Keys: D20200828171350510
Message-ID: <be72f2bc-fac2-df83-12a3-e873945cd38d@towo.net>
Date: Fri, 28 Aug 2020 17:13:50 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <DB7PR02MB3996657CA16B0B48A6DE6114E7520@DB7PR02MB3996.eurprd02.prod.outlook.com>
X-Provags-ID: V03:K1:c4k0IZQnIqUSVWHU1AiWyjZU+/7gqh7iBJOjs0g9rw1gy2c7lDa
 0kSjpRJqMSTBIarKnBULrCQPbBTpc9XMrClwVkuIUuBbzKkvVBrr1WQ15KzvpcslhyaWpWd
 UFKOCVv+a7UEQszj8B7CM3NOaQJuMkFCEhvWaU8ciNLAY20Je0QmGyfLlPWAShC65Rkwmr8
 sGZYWH0JzuWB/uRXZntdg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:a+l+6ep/4pk=:6pG7Bsq8ze2qFhHolHkpDn
 /Na/jt5V6xGy5ggqQaDKB/NqoHtdct3imanLjN5cjrzI5zKnqpRpBqHon0ccd3vuagoBq5GC0
 imrU17wJIi+XCqCzglVXBflHmypQierIb3DBeR7mQbAphVD1kydWm60xEpB+G+UmCf9Hi9U+t
 C891wjXyaYrxk3+IZEYPdBDqsGNbcJ2utjiu78PDJIzC5j6qjRte2QOQS22WqBEEuCPb5Mqnk
 vig2NbmYrjGYaPq/GNWZZXco0q9eL2FTZ+A6deG7B6PGn6Enga+oWX4jRvQajbtGwyoRVfqPx
 EREO6tigc7Zf93Co+cBdlCgYslTOLMRBb9wO8PqniiWT2i9HLjp4NImkLA/lq8AR2mIOgGmo5
 RVG2CgfRSGvfk5gb+vkbjFTAGeKlfHYHJPBTCq4UgVM4PltAOWV3Stqug2x4DMBqZlsmmBrdF
 TD0hkBKfEYKwC5AfeNsUtLFkRv/uMVVEUkda1Uwo9ope3M/iM6Zrp+xPN5tOTPMLdpkgKw8CR
 TQ67jysI1WjlvJvGVuscVhxu5EONqTRFK5s0g/B0SZ/ZeWfS75zagGOvwMR00kH4Y16BcAdg0
 PlPdsnNdkhCTWNFNojhp8jH2Dl2etBfGl2oto1RzfIo9vWM2vWZuGlfPW9t6KmqnN+VJtTJlB
 EkVMoWlqT7yLJjM3pDf5qNjC9aA68jN/VXC2DXqLsAFHzxAoDdztVHHDbzaCgVRdb9SC5QXCz
 0BvsDVwPDMV9UgMlPwnz+ntSX17L6cDFUOEZzWeiYHDtTeeLJ7Z2ktqPSDq/nQzYFjYuhgqUh
 wXVyEeJOmc2i6q4lZHAeZYIEuDzI8zSh8qWsrVkTmQR/lRkgNIkVL5G+sQz7CgZVth02R3H
X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00, BODY_8BITS,
 HTML_MESSAGE, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A,
 RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NONE,
 TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.29
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 07SFEOiJ028631

Am 28.08.2020 um 16:31 schrieb Hamish McIntyre-Bhatty via Cygwin:
> On 28/08/2020 09:33, Thomas Wolff wrote:
>> Am 27.08.2020 um 21:55 schrieb Brian Inglis:
>>> 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?
>> This description is quite fuzzy. It could be that you resized the
>> window while a program was running, or that some background process
>> sends output to the screen asynchronously. In such cases, the shell
>> loses track of the cursor position and line editing fails. That's not
>> a terminal issue.
>>
> My apologies. I mean when a the command with its arguments are long
> enough to wrap around the width of the Mintty window.
That works fine normally but fails under certain additional conditions. 
Please provide a reproducible test case in order to get suitable 
comments. Also, which shell do you use?
Thomas


>>>> 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.
>> This was requested to mintty already
>> (https://github.com/mintty/mintty/issues/82) but it's not a
>> traditional terminal feature, so if some terminals have added it as an
>> enhancement, that's not a "fix".
>> Thomas
>>
> Good to know.
>>>> 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.]
>>>
>> -- 
>> Problem reports:      https://cygwin.com/problems.html
>> FAQ:                  https://cygwin.com/faq/
>> Documentation:        https://cygwin.com/docs.html
>> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
>>
>> --
>> Problem reports:      https://cygwin.com/problems.html
>> FAQ:                  https://cygwin.com/faq/
>> Documentation:        https://cygwin.com/docs.html
>> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple