From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 24995@debbugs.gnu.org
Subject: bug#24995: 25.1; Emacs manual: no doc on "bracketed paste mode"
Date: Thu, 29 Dec 2016 17:51:24 +0200 [thread overview]
Message-ID: <838tqyvimb.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkSHrD6Sf=1cZu9UeA61JD_=pDU86qhrU8JXd9O6vSyoCg@mail.gmail.com> (message from Philipp Stephani on Wed, 28 Dec 2016 21:11:19 +0000)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Wed, 28 Dec 2016 21:11:19 +0000
> Cc: drew.adams@oracle.com, 24995@debbugs.gnu.org
>
> 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.
I disagree, but let's defer to users' complaints (or lack thereof) to
be the judge.
next prev parent reply other threads:[~2016-12-29 15:51 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
2016-12-29 15:51 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838tqyvimb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24995@debbugs.gnu.org \
--cc=p.stephani2@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.