all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Werner LEMBERG <wl@gnu.org>
To: eliz@gnu.org
Cc: 33445@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#33445: Say "U+1F52E"
Date: Wed, 21 Nov 2018 06:44:35 +0100 (CET)	[thread overview]
Message-ID: <20181121.064435.330967170186046743.wl@gnu.org> (raw)
In-Reply-To: <838t1nhzd2.fsf@gnu.org>


>> I second that.  It might be a small difference to people who are
>> well acquainted with Emacs coding systems.  However, I believe that
>> Joe User would prefer the `U+' notation.  (I have a good knowledge
>> of coding systems, and even I would prefer to see the `U+' prefix
>> :-)
> 
> This is not about coding systems at all.  The codepoint is shown at
> least twice in the display, just without the U+ prefix.
> 
> The display produced by that function is already cluttered beyond
> hope, so much so that many important details evade you until you
> actually read each and every symbol.

Well, this is a different issue.

> Adding the U+ to them (where, exactly?) would make aa bad situation
> even worse, for very little gain.
> 
> The proper Unicode name of the character, CRYSTAL BALL, is shown in
> the display.

I would like to see

  U+1F52E CRYSTAL BALL


    Werner





  reply	other threads:[~2018-11-21  5:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 18:50 bug#33445: Say "U+1F52E" 積丹尼 Dan Jacobson
2018-11-20 19:23 ` Eli Zaretskii
2018-11-20 20:04   ` 積丹尼 Dan Jacobson
2018-11-20 20:17     ` Eli Zaretskii
2018-11-20 20:21       ` 積丹尼 Dan Jacobson
2018-11-20 21:46         ` Werner LEMBERG
2018-11-21  3:40           ` Eli Zaretskii
2018-11-21  5:44             ` Werner LEMBERG [this message]
2018-11-21  9:28               ` Eli Zaretskii
2018-11-21 10:36                 ` Werner LEMBERG
2018-11-21 10:59                   ` Eli Zaretskii
2018-11-21  3:34         ` Eli Zaretskii
2018-11-21 12:41 ` 積丹尼 Dan Jacobson
2018-11-21 13:09   ` Eli Zaretskii
2018-11-22 15:32     ` Eli Zaretskii

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=20181121.064435.330967170186046743.wl@gnu.org \
    --to=wl@gnu.org \
    --cc=33445@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.