GNU bug report logs - #25641
25.1; insert-char function inconsistency

Previous Next

Full log

Message #8 received at 25641 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Pablo Mercader Alcántara <programingfrik <at> gmail.com>
Cc: 25641 <at> debbugs.gnu.org
Subject: Re: bug#25641: 25.1; insert-char function inconsistency
Date: Tue, 07 Feb 2017 18:08:48 +0200

> From: Pablo Mercader Alcántara <programingfrik <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.