all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Francesco Potortì" <pot@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>, 67430@debbugs.gnu.org
Subject: bug#67430: 29.1; <Multi_key> is undefined
Date: Sat, 25 Nov 2023 14:18:54 +0100	[thread overview]
Message-ID: <875y1qots1.fsf@tucano.isti.cnr.it> (raw)
In-Reply-To: <83cyvycc99.fsf@gnu.org> (eliz@gnu.org)

>> 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?

In mormal usage, Emacs never even sees <Multi_key>.  I suppose that Emacs, like usual X applications, relies on X to interpret it as a modifier key, and X uses its composition rules.  But Xpra apparently is another piece of cake (at least the version I am using) and it passes the key as-is.  I think that this is unusual behaviour.

If Emacs happens to see <Multi_key>, maybe in principle it should ask X to interpret the subsequent characters using X's composition rules.  I don't know if that's possible in a clean way, I suppose that would not be obvious to do.  Lacking such functionality, I think the only reasonable thing to do is to interpretet is as C-x 8, which has composition rules mostly compatible with those of X.  So in most cases this will be transparent to the user.  I don't see how throwing an error instead can be better.  And yes, in principle users can rebind it.

An alternative would be to bind <Multi_key> to a command which is disabled by default (like for example narrow-to-page), and when enabled does the same as C-x 8.  But I think that binding it by default is simpler and has so rare and technical drawbacks that people caring it about are aware of the issue and can solve it.





  reply	other threads:[~2023-11-25 13: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
2023-11-25 13:18         ` Francesco Potortì [this message]
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=875y1qots1.fsf@tucano.isti.cnr.it \
    --to=pot@gnu.org \
    --cc=67430@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.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.