From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24995@debbugs.gnu.org
Subject: bug#24995: 25.1; Emacs manual: no doc on "bracketed paste mode"
Date: Wed, 28 Dec 2016 21:11:19 +0000 [thread overview]
Message-ID: <CAArVCkSHrD6Sf=1cZu9UeA61JD_=pDU86qhrU8JXd9O6vSyoCg@mail.gmail.com> (raw)
In-Reply-To: <83oa10z3o1.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
Eli Zaretskii <eliz@gnu.org> schrieb am Mo., 28. Nov. 2016 um 04:25 Uhr:
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Sun, 27 Nov 2016 21:11:36 +0000
> > Cc: 24995@debbugs.gnu.org
> >
> > > I do think it would be nice to let users disable use of this
> > > feature, even if the terminal supports it. Since we do that
> > > with other xterm extensions (see xterm-extra-capabilities),
> > > we should probably offer the same level of control for this
> > > capability, either as part of getSelection, or as a separate
> > > feature.
> >
> > Clearly.
> >
> > If Emacs can suddenly start supporting it then Emacs can
> > provide a way to turn it off (it was, in effect, off before).
> >
> > > Philipp, would you like to add this on the emacs-25 branch?
> >
> > Yes, thank you.
> >
> > There shouldn't be any need for turning off bracketed pasting. It's just
> a separate input key sequence that is
> > either sent or not sent by the terminal emulator. This isn't different
> from e.g. the Hyper key; there's also no
> > option to disable the latter.
>
> That is true, but we still allow the user to control the other similar
> extensions, which all fit your description. So why should support for
> bracketed paste mode be different? It's inconsistent, and I can't
> think of a reason why we would want this inconsistency.
>
I don't think that inconsistency is a strong enough reason to introduce a
customization option, especially for a setting that has no user-visible
behavior. There are certainly several other optimizations in the the Emacs
code base that can't be turned off.
[-- Attachment #2: Type: text/html, Size: 2752 bytes --]
next prev parent reply other threads:[~2016-12-28 21:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<81ea90bf-11b8-4316-94b4-2815222b95d9@default>
[not found] ` <<83vave5fbr.fsf@gnu.org>
2016-11-23 16:42 ` bug#24995: 25.1; Emacs manual: no doc on "bracketed paste mode" Drew Adams
2016-11-27 21:11 ` Philipp Stephani
2016-11-28 3:25 ` Eli Zaretskii
2016-12-28 21:11 ` Philipp Stephani [this message]
2016-12-29 15:51 ` Eli Zaretskii
2016-11-23 2:50 Drew Adams
2016-11-23 3:26 ` Drew Adams
2016-11-23 16:30 ` Eli Zaretskii
2019-11-11 3:19 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAArVCkSHrD6Sf=1cZu9UeA61JD_=pDU86qhrU8JXd9O6vSyoCg@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=24995@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).