From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "Philipp Stephani" <p.stephani2@gmail.com>,
25005@debbugs.gnu.org,
"Clément Pit--Claudel" <clement.pit@gmail.com>
Subject: bug#25005: 25.1; Support disabling bracketed paste mode.
Date: Fri, 04 Feb 2022 10:59:50 +0100 [thread overview]
Message-ID: <87mtj77y09.fsf@gmail.com> (raw)
In-Reply-To: <87v8xvlm19.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 03 Feb 2022 21:42:26 +0100")
>>>>> On Thu, 03 Feb 2022 21:42:26 +0100, Lars Ingebrigtsen <larsi@gnus.org> said:
Lars> Philipp Stephani <p.stephani2@gmail.com> writes:
>> "My crystal ball said you should remove (global-set-key (kbd "M-[")
>> 'previous-multiframe-window) from your ~/.emacs. You might like to M-x
>> report-emacs-bug and ask for global-set-key to complain when the key
>> sequence conflicts with something in input-decode-map (as is the case
>> here, because the byte sequence ESC [ (which corresponds to the M-[
>> event) is used by text terminal as a prefix for encoding all kinds of
>> special events)."
Lars> This would be easy enough to do... does anybody have any comments?
Hmm, so if I start emacs under a window system, where input-decode-map
doesnʼt contain ESC [, and then create a tty frame inside an xterm,
this would still fail, no? Or did you want the terminal setup to
complain if input-decode-map conflicts with a key binding as well?
And no doubt there are daemon use-cases to consider as well.
Robert
--
next prev parent reply other threads:[~2022-02-04 9:59 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 [this message]
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=87mtj77y09.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=25005@debbugs.gnu.org \
--cc=clement.pit@gmail.com \
--cc=larsi@gnus.org \
--cc=p.stephani2@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).