From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 46240@debbugs.gnu.org
Subject: bug#46240: Sorting order of read-char-by-name
Date: Tue, 02 Feb 2021 19:16:00 +0200 [thread overview]
Message-ID: <87lfc666vr.fsf@mail.linkov.net> (raw)
In-Reply-To: <875z3aooao.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 02 Feb 2021 09:40:31 +0100")
>> The current order, while it doesn't follow the order of the characters
>> within the script, makes it very easy to find the character for anyone
>> who knows English (more generally, Latin) alphabet. So I'm not sure
>> the proposed change is necessarily for the better, at least not in all
>> the use cases.
>
> I agree -- sorting by the Unicode character names is better here, I
> think.
>
> The command is for inserting characters you don't use constantly
> (because if you did, you'd use a different input method that made those
> characters more readily available), which means that you probably aren't
> super-familiar with them. So you'd be looking at the (English)
> descriptions of the characters to find the one you want.
Indeed, the English descriptions help to identify the characters.
But the problem is that currently characters of one Unicode block
are scattered among the whole list.
For example, in 'C-x 8 RET SUPER TAB' the character SUPERHERO
from the Unicode block 'Supplemental Symbols and Pictographs'
currently is displayed at the beginning of the long list of
SUPERSCRIPT characters from the block 'Superscripts and Subscripts',
but its counterpart character SUPERVILLAIN is displayed
at the end of the long list of SUPERSCRIPT characters.
Whereas while sorting them by their codepoints, characters
of the same Unicode block come together:
🦸 SUPERHERO
🦹 SUPERVILLAIN
next prev parent reply other threads:[~2021-02-02 17:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 17:23 bug#46240: Sorting order of read-char-by-name Juri Linkov
2021-02-01 17:41 ` Eli Zaretskii
2021-02-02 8:40 ` Lars Ingebrigtsen
2021-02-02 17:16 ` Juri Linkov [this message]
2021-02-02 17:57 ` bug#46240: [External] : " Drew Adams
2021-02-02 18:47 ` Eli Zaretskii
2021-02-03 15:38 ` Lars Ingebrigtsen
2021-02-03 18:02 ` Lars Ingebrigtsen
2021-02-03 18:17 ` Eli Zaretskii
2021-02-03 18:21 ` Lars Ingebrigtsen
2021-02-03 18:40 ` Eli Zaretskii
2021-02-03 19:43 ` Juri Linkov
2021-02-04 7:56 ` Lars Ingebrigtsen
2021-02-04 9:32 ` Juri Linkov
2021-02-04 16:19 ` Lars Ingebrigtsen
2021-02-04 22:34 ` Juri Linkov
2021-02-05 7:36 ` Eli Zaretskii
2021-02-06 19:35 ` Juri Linkov
2021-02-06 20:01 ` Eli Zaretskii
2021-02-07 18:56 ` Juri Linkov
2021-02-07 19:54 ` Eli Zaretskii
2021-02-09 18:13 ` Juri Linkov
2021-02-09 19:00 ` Eli Zaretskii
2021-02-09 19:16 ` Juri Linkov
2021-02-02 17:13 ` Juri Linkov
2021-02-02 18:44 ` Eli Zaretskii
2021-02-03 17:27 ` Juri Linkov
2021-02-03 17:54 ` Eli Zaretskii
2021-02-03 19:44 ` Juri Linkov
2021-02-03 15:35 ` Lars Ingebrigtsen
2021-02-01 19:35 ` bug#46240: [External] : " Drew Adams
2021-02-02 17:18 ` Juri Linkov
2021-02-02 17:49 ` Drew Adams
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=87lfc666vr.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=46240@debbugs.gnu.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 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.