From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Brian Julin <BJulin@clarku.edu>, 28868@debbugs.gnu.org
Subject: bug#28868: 25.1; Feature request: isolate kill ring from window system cut and paste buffer
Date: Sun, 29 Oct 2017 16:24:46 +0000 [thread overview]
Message-ID: <CAArVCkQUZsyjb9ra=qDYaxbEz8LoQc2BMxsrs9hPL8fvbZMFaw@mail.gmail.com> (raw)
In-Reply-To: <83efq2gbv6.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
Eli Zaretskii <eliz@gnu.org> schrieb am Mo., 16. Okt. 2017 um 20:58 Uhr:
> > From: Brian Julin <BJulin@clarku.edu>
> > Date: Mon, 16 Oct 2017 18:11:29 +0000
> >
> > Ever since xterm.el added bracketed paste mode support, the #6 yank
> > yanks the line of text which was pasted. Though this is stated in the
> > code comments as the desired behavior, it certainly is not the way I
> > personally wish emacs to behave. I much prefer the window system
> > clipboard and selection system to have absolutely nothing to do at all
> > with the emacs kill-ring (unless I run a command like x-clipboard-yank
> > explicitly.)
> >
> > Normally when an upgrade starts behaving in a new and upsetting
> > manner, I would google and find, after quite a tedious process of
> > reading random forum threads for tangentially related issues until
> > I find one that actually addresses my issue, that there was a
> configuration
> > variable available for my /etc/site-start.d files to customize such a
> behavior.
> > In this case there appears to be none.
>
> Thank you for your report. Would you be willing to submit a patch
> that introduces a defcustom which will allow to disable bracketed
> paste mode even if the terminal support it?
>
>
Does this need a new user option, or shouldn't the behavior rather respect
the value of `select-enable-clipboard'?
[-- Attachment #2: Type: text/html, Size: 1796 bytes --]
next prev parent reply other threads:[~2017-10-29 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 18:11 bug#28868: 25.1; Feature request: isolate kill ring from window system cut and paste buffer Brian Julin
2017-10-16 18:56 ` Eli Zaretskii
2017-10-16 20:20 ` Brian Julin
2017-10-29 16:24 ` Philipp Stephani [this message]
2017-10-29 18:26 ` Eli Zaretskii
2021-09-03 7:47 ` Lars Ingebrigtsen
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='CAArVCkQUZsyjb9ra=qDYaxbEz8LoQc2BMxsrs9hPL8fvbZMFaw@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=28868@debbugs.gnu.org \
--cc=BJulin@clarku.edu \
--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).