unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 27544@debbugs.gnu.org, itai.berli@gmail.com
Subject: bug#27544: 25.1; Visualization of Unicode bidirectional marks
Date: Wed, 01 Dec 2021 19:53:54 +0200	[thread overview]
Message-ID: <83wnkoqki5.fsf@gnu.org> (raw)
In-Reply-To: <87bl20jkg7.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  01 Dec 2021 18:36:56 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: itai.berli@gmail.com,  27544@debbugs.gnu.org
> Date: Wed, 01 Dec 2021 18:36:56 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Thanks.  But wouldn't glyphless-hex-display-mode be a better name?
> > glyphless-display-mode doesn't really say what it does to glyphless
> > characters.
> 
> It doesn't hexify the glyphs, it uses `acronym'.  But I thought we might
> allow that to be customised if somebody asks for it, which is why it's
> not called `glyphless-acronym-display-mode'.

But glyphless-display-mode has no mnemonic value.  We already display
glyphless characters, so this name doesn't help at all.

Does anyone have suggestions for a better name?





  reply	other threads:[~2021-12-01 17:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-01  9:58 bug#27544: 25.1; Visualization of Unicode bidirectional marks Itai Berli
2017-07-01 10:36 ` Eli Zaretskii
2017-07-01 11:48 ` Itai Berli
2017-07-01 12:16   ` Eli Zaretskii
2017-07-01 12:36 ` Itai Berli
2017-07-01 12:51   ` Eli Zaretskii
2021-12-01  4:55 ` Lars Ingebrigtsen
2021-12-01  7:48   ` Eli Zaretskii
2021-12-01 15:51     ` bug#27544: [External] : " Drew Adams
2021-12-01 15:53     ` Lars Ingebrigtsen
2021-12-01 17:12       ` Eli Zaretskii
2021-12-01 17:36         ` Lars Ingebrigtsen
2021-12-01 17:53           ` Eli Zaretskii [this message]
2021-12-02  9:04             ` Juri Linkov
2021-12-15 18:14               ` Filipp Gunbin

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=83wnkoqki5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=27544@debbugs.gnu.org \
    --cc=itai.berli@gmail.com \
    --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).