From: Eli Zaretskii <eliz@gnu.org>
To: "Pablo Mercader Alcántara" <programingfrik@gmail.com>
Cc: 25641@debbugs.gnu.org
Subject: bug#25641: 25.1; insert-char function inconsistency
Date: Tue, 07 Feb 2017 18:08:48 +0200 [thread overview]
Message-ID: <83tw8656gf.fsf@gnu.org> (raw)
In-Reply-To: <CAPQ4eMLyZGv7OH4g9H2cYTy+1mUQyr3+RmGW5YubanKeLzyf8Q@mail.gmail.com> (message from Pablo Mercader Alcántara on Tue, 7 Feb 2017 09:04:01 -0400)
> From: Pablo Mercader Alcántara <programingfrik@gmail.com>
> Date: Tue, 7 Feb 2017 09:04:01 -0400
>
> Character code properties: customize what to show
> old-name: BELL
> general-category: Cc (Other, Control)
> [...]
> Character code properties: customize what to show
> name: BELL
> general-category: So (Symbol, Other)
> decomposition: (128276) ('🔔')
>
> Its a different character but it also states that I could write it using
> C-x 8 RET BELL. To me that is an inconsistency, because one of the
> commands that the help screen showed me was C-x 8 RET BELL and that
> clearly doesn't work.
It's not an inconsistency: the first one has BELL as its "old name"
property (and has no "name" property), the second one as its "name"
property. This is per Unicode definitions in their character
database, which Emacs uses for this feature. Unicode removed the
names of low control characters in some version of their standard,
leaving the "old name" behind for compatibility.
Emacs displays "old name" if "name" is missing.
If you type "C-x 8 RET BELL" and hit TAB right after that, Emacs will
tell you this is "complete, but not unique". Another TAB will pop up
the list of completion candidates, where you will see both BELLs (and
a couple more characters).
I don't think there's a bug here.
Thanks.
next prev parent reply other threads:[~2017-02-07 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 13:04 bug#25641: 25.1; insert-char function inconsistency Pablo Mercader Alcántara
2017-02-07 16:08 ` Eli Zaretskii [this message]
2017-02-07 17:04 ` Stephen Berman
2017-02-08 0:45 ` Pablo Mercader Alcántara
2017-02-08 13:15 ` Stephen Berman
2017-02-08 17:54 ` Eli Zaretskii
2017-02-08 21:43 ` Stephen Berman
2017-02-08 22:01 ` Pablo Mercader Alcántara
2017-02-09 14:15 ` Stephen Berman
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=83tw8656gf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25641@debbugs.gnu.org \
--cc=programingfrik@gmail.com \
/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).