all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Brian Julin <BJulin@clarku.edu>
Cc: 28868@debbugs.gnu.org
Subject: bug#28868: 25.1; Feature request: isolate kill ring from window system cut and paste buffer
Date: Mon, 16 Oct 2017 21:56:45 +0300	[thread overview]
Message-ID: <83efq2gbv6.fsf@gnu.org> (raw)
In-Reply-To: <BLUPR03MB582724C305348AB44D7C28BB44F0@BLUPR03MB582.namprd03.prod.outlook.com> (message from Brian Julin on Mon, 16 Oct 2017 18:11:29 +0000)

> 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?





  reply	other threads:[~2017-10-16 18:56 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 [this message]
2017-10-16 20:20   ` Brian Julin
2017-10-29 16:24   ` Philipp Stephani
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83efq2gbv6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=28868@debbugs.gnu.org \
    --cc=BJulin@clarku.edu \
    /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.