From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Mintty text glitches when using up key
Date: Fri, 28 Aug 2020 18:45:54 +0200 [thread overview]
Message-ID: <f77ae080-21d7-1942-c9c6-502b8e66be4b@towo.net> (raw)
In-Reply-To: <DB7PR02MB3996806D594D4D525D20CEF7E7520@DB7PR02MB3996.eurprd02.prod.outlook.com>
Am 28.08.2020 um 17:48 schrieb Hamish McIntyre-Bhatty via Cygwin:
> On 28/08/2020 16:13, Thomas Wolff wrote:
>> Am 28.08.2020 um 16:31 schrieb Hamish McIntyre-Bhatty via Cygwin:
>>> 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
> Okay, I'll see if I can come up with a test case.
>
> If I can, would it be better for me to file a bug on GitHub for this as well?
Likely not as I firmly believe it's not a terminal issue.
>
> Hamish
>
>
> --
> 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
next prev parent reply other threads:[~2020-08-28 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 16:55 Hamish McIntyre-Bhatty
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 [this message]
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=f77ae080-21d7-1942-c9c6-502b8e66be4b@towo.net \
--to=towo@towo.net \
--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).