From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Francesco Potortì" <pot@gnu.org>
Cc: 67430@debbugs.gnu.org
Subject: bug#67430: 29.1; <Multi_key> is undefined
Date: Sat, 25 Nov 2023 07:47:49 +0800 [thread overview]
Message-ID: <s7r5y1q7ly2.fsf@yahoo.com> (raw)
In-Reply-To: <878r6npfu5.fsf@tucano.isti.cnr.it> ("Francesco Potortì"'s message of "Fri, 24 Nov 2023 12:10:10 +0100")
Francesco Potortì <pot@gnu.org> writes:
> When I run Emacs I can use the X compose key. Apparently X interprets
> it so that it is invisible to Emacs, and in fact I cannot see it in
> the lossage.
>
> When I run Emacs over Xpra, apparently Xpra passes the compose key to
> Emacs. I would expect it to do the same as C-x8 does, but this is not
> the case. In fact, I get the error message "<Multi_key> is
> undefined".
>
> I just corrected the problem with (keymap-global-set "<Multi_key>"
> iso-transl-ctl-x-8-map), but I wonder why this is necessary at all. I
> think this binding should be the default.
Multi_key isn't uniformly the Compose key, so I'd rather not make such
rash choices. My opinion isn't particularly strong in this regard,
however, and perhaps this isn't a one-off. If anyone reading this has
experienced such problems before, please make yourself known.
next prev parent reply other threads:[~2023-11-24 23:47 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s7r5y1q7ly2.fsf@yahoo.com \
--to=bug-gnu-emacs@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 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.