From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: libreadline{7,-devel} 8.1 (problem of octave-gui)
Date: Fri, 10 Sep 2021 11:45:58 -0600 [thread overview]
Message-ID: <5d82b938-5888-da78-1ed1-cc909846a04d@SystematicSw.ab.ca> (raw)
In-Reply-To: <87y284xwak.fsf@Otto.invalid>
On 2021-09-10 09:52, ASSI wrote:
> Takashi Yano via Cygwin writes:
>>> h. Bracketed paste mode is enabled by default. There is a configure-time
>>> option (--enable-bracketed-paste-default) to set the default to on or off.
>> Does libreadline7 (8.1) break compatibility with old one?
>> Reverting libreadline7 to 7.0.3-3 solves the issue.
>>
>> Setting
>> set enable-bracketed-paste off
>> in ~/.inputrc also solves the problem.
>
> Well, one obvious way of solving the issue would be to use the configure
> option of not enabling bracketed paste by default. Although it would be
> better in the long term if the applications learn to use it correctly…
The default was changed as documented to avoid potential security
issues: what could go wrong if you copied "rm -rf /..." not selecting
the ... and pasted it including the "\n", or the source (e.g. javascript
malware) added a few such commands for different systems to the copy! ;^>
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2021-09-10 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 18:25 [ANNOUNCEMENT] Updated: libreadline{7,-devel} 8.1 Cygwin readline Co-Maintainer
2021-09-10 12:56 ` [ANNOUNCEMENT] Updated: libreadline{7,-devel} 8.1 (problem of octave-gui) Takashi Yano
2021-09-10 15:52 ` ASSI
2021-09-10 17:45 ` Brian Inglis [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=5d82b938-5888-da78-1ed1-cc909846a04d@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).