From: Fergus Daly <fergusd84@outlook.com>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Cc: Fergus Daly <fergusd84@outlook.com>, "towo@towo.net" <towo@towo.net>
Subject: Re: [ANNOUNCEMENT] Updated: mintty 3.1.8
Date: Fri, 12 Jun 2020 10:36:21 +0000 [thread overview]
Message-ID: <AM6PR03MB5282C84F56DB39BDF92BF940A4810@AM6PR03MB5282.eurprd03.prod.outlook.com> (raw)
Glitch?
Sorry: I acknowledge that this is maximally unhelpful through lacking a worked example,
but just in case it triggers a MeToo with others, that can be better described and/or is replicable.
I start Cygwin with mintty v.3.1.8.
I start an application (actually a stats package) at the mintty prompt.
From within the application, edit a library file by calling nano. Save file and exit nano.
Still from within the application, all subsequent uses of nano (any file) present a corrupted file,
starting with line j, followed by j blank lines then line j+1.
(j alters from time to time, round about 15-20.)
Press PgDn to get past the blanks, then press PgUp to start of file: this works
(i.e. recovers the complete file for editing) with the minor glitch that line j is still printed
(but inaccessible) at start-of-file - like some kind of title banner.
Conceivably this has revealed a hitherto concealed mis-match between the application and/or nano
- but this phenomenon started immediately after a couple of mintty updates ago, and the same procedure
Of editing-within-the-application works entirely glitch-free within bash, and within xterm.
Again, sorry for non-replicable glitch - I'll keep trying - and sincere apols to Thomas Wolff if the glitch
resides elsewhere than mintty - but it would be good to get any similar accounts.
next reply other threads:[~2020-06-12 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 10:36 Fergus Daly [this message]
2020-06-12 10:55 ` Fergus Daly
-- strict thread matches above, loose matches on Subject: below --
2020-06-08 17:24 Thomas Wolff
2020-06-09 11:15 ` Enrico Forestieri
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=AM6PR03MB5282C84F56DB39BDF92BF940A4810@AM6PR03MB5282.eurprd03.prod.outlook.com \
--to=fergusd84@outlook.com \
--cc=cygwin@cygwin.com \
--cc=towo@towo.net \
/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).