From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Longfilename problem with mintty 3.6.0
Date: Tue, 29 Mar 2022 12:45:16 +0200 [thread overview]
Message-ID: <2a40c550-23ae-bac1-0072-79861e70dc4b@towo.net> (raw)
In-Reply-To: <DB6P18901MB005589C669AF0EC94771B16DA41E9@DB6P18901MB0055.EURP189.PROD.OUTLOOK.COM>
Am 29.03.2022 um 11:16 schrieb Fergus Daly:
>>> I'm having difficulty with longfilename in the latest mintty.
>>> This is new since 3.6.0.
Automatic line wrap-around (not "rewrap") can be turned on/off
dynamically by an escape sequence. This may result in unexpected
behaviour if an application is terminated irregularly, so it does not
restore modes.
Also it happens that a terminal resize, while in an application, is not
propagated to the shell, so it continues with a wrong line width assumption.
>
> Sorry. On a different machine, no difficulties. Possibly (or even likely) a local problem.
> Apologies for sending.
>
prev parent reply other threads:[~2022-03-29 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 8:04 Fergus Daly
2022-03-29 9:16 ` Fergus Daly
2022-03-29 10:45 ` 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=2a40c550-23ae-bac1-0072-79861e70dc4b@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).