From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50272@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#50272: describe-char and C-u C-x = neglect mentioning anything about width
Date: Tue, 31 Aug 2021 15:34:26 +0300 [thread overview]
Message-ID: <837dg1u71p.fsf@gnu.org> (raw)
In-Reply-To: <87czpu76lz.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 31 Aug 2021 03:20:08 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 積丹尼 Dan Jacobson <jidanni@jidanni.org>,
> 50272@debbugs.gnu.org
> Date: Tue, 31 Aug 2021 03:20:08 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > You mean, you'd like to see which characters are "double-width"? 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).
> >
> > The width information is only more-or-less accurate on text-mode
> > terminals. I wonder how to avoid confusing users with this.
> >
> > Does anyone have ideas?
>
> We could have the command only mention the double-width-ness on
> terminals?
I don't think this is what the OP wants.
next prev parent reply other threads:[~2021-08-31 12:34 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 [this message]
2021-08-31 13:58 ` 積丹尼 Dan Jacobson
2022-08-22 16:52 ` Lars Ingebrigtsen
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=837dg1u71p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50272@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.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).