From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50272@debbugs.gnu.org, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#50272: describe-char and C-u C-x = neglect mentioning anything about width
Date: Mon, 22 Aug 2022 18:52:04 +0200 [thread overview]
Message-ID: <8735do2pcb.fsf@gnus.org> (raw)
In-Reply-To: <83fsuqkjcz.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 Aug 2021 19:06:20 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> describe-char and C-u C-x = neglect mentioning anything about width. Try
>> them on
>> $ unicode --max 0 --brief -r BOX.*X
>> ☒ U+2612 BALLOT BOX WITH X
>> ⮽ U+2BBD BALLOT BOX WITH LIGHT X
>> 🗵 U+1F5F5 BALLOT BOX WITH SCRIPT X
>> 🗷 U+1F5F7 BALLOT BOX WITH BOLD SCRIPT X
>> They go into great detail, but miss mentioning width.
>
> You mean, you'd like to see which characters are "double-width"?
All of these are "single-width", as far as I can tell?
(elt char-width-table ?⮽)
=> 1
We mostly have the double-widthness for East Asian characters:
(elt char-width-table ?㊟)
=> 2
> We could add that, but on GUI frames that would just confuse, because
> those "double-width" characters more often than not take less than two
> full columns, especially if you happen to use variable-pitch font for
> such exotic characters (something that happens quite a lot).
That, in conjunction with all so many characters being wider visually
than the "double-width" characters makes me thing that displaying this
information would just be confusing all around. So I'm closing this as
a "wontfix".
prev parent reply other threads:[~2022-08-22 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 13:13 bug#50272: describe-char and C-u C-x = neglect mentioning anything about width 積丹尼 Dan Jacobson
2021-08-30 16:06 ` Eli Zaretskii
2021-08-31 1:20 ` Lars Ingebrigtsen
2021-08-31 12:34 ` Eli Zaretskii
2021-08-31 13:58 ` 積丹尼 Dan Jacobson
2022-08-22 16:52 ` Lars Ingebrigtsen [this message]
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=8735do2pcb.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50272@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jidanni@jidanni.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.