From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: spacibba@aol.com, juri@linkov.net, emacs-devel@gnu.org
Subject: Re: xterm [menu] key definition
Date: Wed, 25 Aug 2021 18:41:59 -0400 [thread overview]
Message-ID: <jwvtujd2m5t.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83o89lvju4.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 25 Aug 2021 14:34:43 +0300")
> Yes. Which is why I wouldn't recommend touching it with a 3-mile pole.
I took it as a dare and thus pushed Ergus's proposed change (duly
decorated with a bit of the story behind it).
It's true that it may break someone's habits somewhere but I think the
new binding at least has the virtue of having a documented justification
for it, and it may prove beneficial to a few other users.
Given the amount of discussion it raised, it feels like it deserves
a NEWS entry, yet when I tried to write it I ended up with:
** The escape sequence '\e[29~' in xterm is now mapped to 'menu'
Xterm sends this sequence for both 'F16' and 'Menu' keys.
It used to be mapped to 'print' but we couldn't find a terminal
that uses this sequence for any kind of 'Print' key.
which seems so obscure that I'm not sure it's more helpful than harmful.
Opinion?
Stefan
next prev parent reply other threads:[~2021-08-25 22:41 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210819024728.kgnf6jmpakqdto4p.ref@Ergus>
2021-08-19 2:47 ` xterm [menu] key definition Ergus
2021-08-23 17:53 ` Ergus
2021-08-24 6:37 ` Juri Linkov
2021-08-24 8:19 ` Ergus
2021-08-24 8:34 ` tomas
2021-08-24 9:17 ` Ergus
2021-08-24 10:03 ` Andreas Schwab
2021-08-24 11:00 ` tomas
2021-08-24 15:30 ` Ergus
2021-08-25 7:06 ` tomas
2021-08-25 9:32 ` Ergus
2021-08-25 10:47 ` tomas
2021-08-25 11:31 ` Ergus
2021-08-26 5:47 ` chad
2021-08-26 7:14 ` tomas
2021-08-26 8:16 ` Andreas Schwab
2021-08-24 8:34 ` Andreas Schwab
2021-08-24 9:07 ` Ergus
2021-08-24 22:05 ` Stefan Monnier
2021-08-25 6:38 ` tomas
2021-08-25 9:04 ` Ergus
2021-08-24 16:40 ` Ergus via Emacs development discussions.
2021-08-24 17:28 ` Eli Zaretskii
2021-08-24 18:09 ` Juri Linkov
2021-08-24 20:23 ` Ergus
2021-08-25 11:27 ` Eli Zaretskii
2021-08-25 11:53 ` Ergus
2021-08-24 22:16 ` Stefan Monnier
2021-08-24 23:20 ` Ergus
2021-08-25 2:53 ` Stefan Monnier
2021-08-25 8:58 ` Ergus
2021-08-25 14:13 ` Stefan Monnier
2021-08-25 11:34 ` Eli Zaretskii
2021-08-25 22:41 ` Stefan Monnier [this message]
2021-08-26 6:55 ` Eli Zaretskii
2021-08-26 7:17 ` Ergus
2021-08-26 7:23 ` Eli Zaretskii
2021-08-26 12:52 ` Ergus
2021-08-26 13:48 ` Eli Zaretskii
2021-08-26 13:59 ` Stefan Monnier
2021-08-26 14:51 ` Andreas Schwab
2021-08-26 15:52 ` Eli Zaretskii
2021-08-25 7:10 ` tomas
2021-08-25 8:02 ` Andreas Schwab
2021-08-25 6:36 ` Yuri Khan
2021-08-25 7:17 ` tomas
2021-08-25 9:00 ` Ergus
2021-08-25 14:01 ` Olaf Rogalsky
[not found] ` <87k0kcovp4.fsf@no.workgroup>
2021-08-25 12:09 ` Gregor Zattler
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=jwvtujd2m5t.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=spacibba@aol.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 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.