all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Brian Julin <BJulin@clarku.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "28868@debbugs.gnu.org" <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 20:20:38 +0000	[thread overview]
Message-ID: <BLUPR03MB5822DD0EB2F47DF9E9AB088B44F0@BLUPR03MB582.namprd03.prod.outlook.com> (raw)
In-Reply-To: <83efq2gbv6.fsf@gnu.org>


Eli Zaretskii worte:

> > From: Brian Julin <BJulin@clarku.edu>
> > Date: Mon, 16 Oct 2017 18:11:29 +0000
> >
> > 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?

Well, A) I've probably only written 20 lines of LISP in my life and
B) Entirely disabling bracketed paste mode and this are a bit orthogonal...
there's a case for both to be sure, given bracketed paste mode is
arguably the wrong side on which (and method with which) to fix the
paste-hijacking security issue and you may want paren-finding and other
things turned on during a paste for some reason.  Also C) I think it's a design
issue that maybe deserves some discussion rather than arbitrarily adding
more spaghetti variables/directives.





  reply	other threads:[~2017-10-16 20:20 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 [this message]
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=BLUPR03MB5822DD0EB2F47DF9E9AB088B44F0@BLUPR03MB582.namprd03.prod.outlook.com \
    --to=bjulin@clarku.edu \
    --cc=28868@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 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.