From: Eli Zaretskii <eliz@gnu.org>
To: Jay Lee <jay@hanjaelee.com>
Cc: 25005@debbugs.gnu.org
Subject: bug#25005: 25.1; Support disabling bracketed paste mode.
Date: Thu, 24 Nov 2016 18:06:45 +0200 [thread overview]
Message-ID: <83h96w6ewa.fsf@gnu.org> (raw)
In-Reply-To: <A1473EFC-3892-4E15-B022-128C6BA34BC6@hanjaelee.com> (message from Jay Lee on Thu, 24 Nov 2016 09:27:31 +0900)
> From: Jay Lee <jay@hanjaelee.com>
> Date: Thu, 24 Nov 2016 09:27:31 +0900
> Cc: 25005@debbugs.gnu.org
>
> 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.
The bracketed paste sequence also starts with M-[, so when you paste,
Emacs invokes previous-multiframe-window instead of the function that
handles the paste. The function that handles the paste knows about
the “200~201~” stuff, and removes it from the pasted text. But
previous-multiframe-window doesn't.
> So in this case, is my emacs bracketed paste mode disabled?
No, I think it's enabled. That's why you get those garbled characters
when you paste.
> if so I want to know why bracketed paste mode is disabled. I just remove configuration for keybinding.
When you remove the key binding, bracketed pastes should work
correctly. Do they?
> And is there way to turn off bracketed paste mode officially?
No, not yet. Not through Emacs, anyway.
prev parent reply other threads:[~2016-11-24 16:06 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
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 [this message]
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=83h96w6ewa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25005@debbugs.gnu.org \
--cc=jay@hanjaelee.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).