From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 67430@debbugs.gnu.org, pot@gnu.org
Subject: bug#67430: 29.1; <Multi_key> is undefined
Date: Sat, 25 Nov 2023 13:18:10 +0200 [thread overview]
Message-ID: <83cyvycc99.fsf@gnu.org> (raw)
In-Reply-To: <8734wuccmg.fsf@yahoo.com> (message from Po Lu on Sat, 25 Nov 2023 19:10:15 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: pot@gnu.org, 67430@debbugs.gnu.org
> Date: Sat, 25 Nov 2023 19:10:15 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > What other roles does this key play? And how frequent is each role?
>
> I don't know. There is generally no other use for it under X, except
> perhaps as a modifier key, which if true Emacs won't register key
> presses at all.
>
> > Also, if we bind this key by default as Francesco suggests, what
> > adverse results could this cause on the systems where this binding is
> > wrong?
>
> Nothing beyond the obvious, to wit: Emacs will react to pressing the
> Multi_key as though it were bound to iso-transl-ctl-x-8-map.
Then maybe we should behave by default as Francesco suggested? users
which don't like the results could always unbind/rebind the key.
WDYT?
next prev parent reply other threads:[~2023-11-25 11:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 11:10 bug#67430: 29.1; <Multi_key> is undefined Francesco Potortì
2023-11-24 23:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-25 8:19 ` Eli Zaretskii
2023-11-25 11:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-25 11:18 ` Eli Zaretskii [this message]
2023-11-25 13:18 ` Francesco Potortì
2023-11-26 1:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-26 10:44 ` Eli Zaretskii
2023-11-28 11:17 ` Francesco Potortì
2023-11-28 14:32 ` Eli Zaretskii
2023-11-29 10:25 ` Francesco Potortì
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=83cyvycc99.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67430@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=pot@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 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).