unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 42256-done@debbugs.gnu.org
Subject: bug#42256: 27.0.50; composition
Date: Thu, 09 Jul 2020 20:51:48 +0300	[thread overview]
Message-ID: <83tuygpoej.fsf@gnu.org> (raw)
In-Reply-To: <E1jtMoR-0005v6-EB@fencepost.gnu.org> (message from Richard Stallman on Wed, 08 Jul 2020 23:01:27 -0400)

> From: Richard Stallman <rms@gnu.org>
> Cc: 42256@debbugs.gnu.org
> Date: Wed, 08 Jul 2020 23:01:27 -0400
> 
>   > I'm not sure I understand what you'd like to see there in addition to
>   > what is shown (the codepoint in hex).  That diamond means that your
>   > terminal cannot display this codepoint, so Emacs cannot usefully show
>   > you what it looks like
> 
> I did not say "show", I said "say":

Please forgive me for not getting this fine nuance of what you said.
We frequently use "say" meaning something a program displays (as in
"Emacs says this:" etc.), so it was easy for me to misunderstand.

> If that diamond were not inside a composition, I could use C-u C-x =
> on it and find out what character that is.  The flaw here is that
> there is no way to see the descriptive name of the second character in
> a composition.

As I said, you can "C-u C-x =" on that diamond in the *Help* buffer,
but I agree that it would be handy to have the info shown
automatically.

> I would like C-u C-x = on a composed charadcter to show the name for
> each character in the composition.

OK, I've now added the names of the characters to the composition
information display on TTY frames.  From now on Emacs will say in this
case:

  Composed with the following character(s) "̄" by these characters:
   u (#x75) LATIN SMALL LETTER U
   ̄ (#x304) COMBINING MACRON

I'm therefore closing this bug report.





  reply	other threads:[~2020-07-09 17:51 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 [this message]
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
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=83tuygpoej.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=42256-done@debbugs.gnu.org \
    --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).