From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: rms@gnu.org, 42256@debbugs.gnu.org
Subject: bug#42256: 27.0.50; composition
Date: Mon, 13 Jul 2020 06:37:52 +0300 [thread overview]
Message-ID: <831rlgnkz3.fsf@gnu.org> (raw)
In-Reply-To: <87365wux23.fsf@mail.linkov.net> (message from Juri Linkov on Mon, 13 Jul 2020 02:35:00 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: 42256@debbugs.gnu.org, rms@gnu.org
> Date: Mon, 13 Jul 2020 02:35:00 +0300
>
> > If someone wants or needs to know which characters participated in a
> > composition on a GUI frame, they can go to those characters in the
> > *Help* buffer and type "C-u C-x =".
>
> It's what I'm doing all the time:
Why do you need that, may I ask? Why is it important to know which
characters were composed, and in what usage scenario?
> > That said, if someone wants to work on adding the character names to
> > the GUI display as well, I won't object.
>
> Ok, done on master in commit 46a0c115f0.
Please also update the Emacs manual, where it describes this display,
because now the text there is outdated.
Thanks.
next prev parent reply other threads:[~2020-07-13 3:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 2:41 bug#42256: 27.0.50; composition Richard Stallman
2020-07-08 14:18 ` Eli Zaretskii
2020-07-09 3:01 ` Richard Stallman
2020-07-09 17:51 ` Eli Zaretskii
2020-07-09 23:36 ` Juri Linkov
2020-07-10 6:21 ` Eli Zaretskii
2020-07-11 2:17 ` Richard Stallman
2020-07-11 23:57 ` Juri Linkov
2020-07-12 15:40 ` Eli Zaretskii
2020-07-12 23:35 ` Juri Linkov
2020-07-13 3:37 ` Eli Zaretskii [this message]
2020-07-13 13:39 ` Eli Zaretskii
2020-07-14 0:13 ` Juri Linkov
2020-07-14 2:36 ` Eli Zaretskii
2020-07-14 23:20 ` Juri Linkov
2020-07-15 14:39 ` Eli Zaretskii
2020-07-15 23:43 ` Juri Linkov
2020-07-16 16:40 ` Eli Zaretskii
2020-07-13 2:56 ` Richard Stallman
2020-07-10 3:52 ` Richard Stallman
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=831rlgnkz3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42256@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=rms@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).