From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: How to debug/troubleshoot mintty?
Date: Wed, 17 Jun 2020 23:12:47 +0200 [thread overview]
Message-ID: <3badb978-f476-1d7a-179b-f68b9a671f4c@towo.net> (raw)
In-Reply-To: <MN2PR17MB3999A58AC703D12624FA2847B89A0@MN2PR17MB3999.namprd17.prod.outlook.com>
Am 17.06.2020 um 21:48 schrieb Allen Hewes via Cygwin:
> Hi,
>
> I seem to be having more screen text redraw/repaint issues with mintty lately (about 6 - 9 months). Generally, it's more often remote systems (via SSH) vs my local client peecee.
>
> My issues range from scrambled up text, cursor in wrong location, cursor line in wrong location and rows/cols changed from initial launch. I have looked at infomcp, stty output and settings. I have compiled new term definitions from Thomas Dickeys ncurses site. I can't seem to find something obvious.
>
> How do I debug/troubleshoot these issues?
Pick *one* example from what you think is wrong, describe it clearly,
and provide a screen log (mintty -l .logfile) that reproduces the issue
with `cat .logfile`.
prev parent reply other threads:[~2020-06-17 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 19:48 Allen Hewes
2020-06-17 21:12 ` Thomas Wolff [this message]
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=3badb978-f476-1d7a-179b-f68b9a671f4c@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).