From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 71411@debbugs.gnu.org
Subject: bug#71411: 30.0.50; Show Unicode names when describing translations
Date: Sat, 08 Jun 2024 16:24:08 +0300 [thread overview]
Message-ID: <86a5jvd0uf.fsf@gnu.org> (raw)
In-Reply-To: <87zfrwhmox.fsf@gmail.com> (message from Robert Pluim on Fri, 07 Jun 2024 16:06:22 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: 71411@debbugs.gnu.org
> Date: Fri, 07 Jun 2024 16:06:22 +0200
>
> >>>>> On Fri, 07 Jun 2024 16:42:01 +0300, Eli Zaretskii <eliz@gnu.org> said:
>
> Eli> What is a "translated binding" or "translated key"? Without
> Eli> explaining that, at least the NEWS entries are not clear enough.
>
> Itʼs anything that goes through `key-translation-map'. How
> about:
>
> -- >8 --
> *** 'C-h k' ('describe-key') shows Unicode name.
> For keybindings which produce single characters via translation (such as
> those using the 'C-x 8' prefix), 'C-h k' now shows the Unicode name of
> the produced character in addition to the character itself, e.g.
Are there any other cases of "translated characters", besides "C-x 8"?
If so, please mention one or two more. If there are no other
examples, I'd remove "such as".
Otherwise, LGTM; please install.
next prev parent reply other threads:[~2024-06-08 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 10:32 bug#71411: 30.0.50; Show Unicode names when describing translations Robert Pluim
2024-06-07 11:08 ` Eli Zaretskii
2024-06-07 12:16 ` Robert Pluim
2024-06-07 13:42 ` Eli Zaretskii
2024-06-07 14:06 ` Robert Pluim
2024-06-08 13:24 ` Eli Zaretskii [this message]
2024-06-10 9:03 ` Robert Pluim
2024-06-10 12:34 ` Eli Zaretskii
2024-06-10 13:01 ` Robert Pluim
2024-06-07 14:01 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-07 14:25 ` Robert Pluim
2024-06-07 14:29 ` Stephen Berman
2024-06-07 14:31 ` Robert Pluim
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=86a5jvd0uf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71411@debbugs.gnu.org \
--cc=rpluim@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).