unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: 25005@debbugs.gnu.org
Subject: bug#25005: 25.1; Support disabling bracketed paste mode.
Date: Thu, 24 Nov 2016 05:37:27 +0200	[thread overview]
Message-ID: <83poll5z0o.fsf@gnu.org> (raw)
In-Reply-To: <a581241a-200d-0921-ec6c-ff01540ad00d@gmail.com> (message from Clément Pit--Claudel on Wed, 23 Nov 2016 22:08:02 -0500)

> From: Clément Pit--Claudel <clement.pit@gmail.com>
> Date: Wed, 23 Nov 2016 22:08:02 -0500
> 
> On 2016-11-23 19:27, Jay Lee wrote:
> > If I start from emacs -q, It works well.
> > I checked again yesterday, I found reason about this issue.
> > 
> > (global-set-key (kbd "M-[") 'previous-multiframe-window) this keybindings affect this issue.
> > after removing this configuration, It works well. Not added “200~201~” I don't understand why is this reason. I think It is just keybinding.
> > 
> > So in this case, is my emacs bracketed paste mode disabled? if so I want to know why bracketed paste mode is disabled. I just remove configuration for keybinding.
> > And is there way to turn off bracketed paste mode officially?
> 
> Stefan responded to your question on stackexchange, and explained why this keybinding was causing issues.

It would be useful to have those explanations here.





  reply	other threads:[~2016-11-24  3:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 14:47 bug#25005: 25.1; Support disabling bracketed paste mode Jay Lee
2016-11-23 16:37 ` Eli Zaretskii
2016-11-24  0:27   ` Jay Lee
2016-11-24  0:55     ` Daniel Colascione
2016-11-24  3:08     ` Clément Pit--Claudel
2016-11-24  3:37       ` Eli Zaretskii [this message]
2016-11-27 20:42         ` Philipp Stephani
2022-02-03 20:42           ` Lars Ingebrigtsen
2022-02-04  9:59             ` Robert Pluim
2022-02-05  6:41               ` Lars Ingebrigtsen
2016-11-24 16:06     ` Eli Zaretskii

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=83poll5z0o.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=25005@debbugs.gnu.org \
    --cc=clement.pit@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 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).