From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 46240@debbugs.gnu.org
Subject: bug#46240: Sorting order of read-char-by-name
Date: Mon, 01 Feb 2021 19:41:07 +0200 [thread overview]
Message-ID: <83wnvr65zg.fsf@gnu.org> (raw)
In-Reply-To: <87v9bb4tm2.fsf@mail.linkov.net> (message from Juri Linkov on Mon, 01 Feb 2021 19:23:41 +0200)
> From: Juri Linkov <juri@linkov.net>
> Date: Mon, 01 Feb 2021 19:23:41 +0200
>
> After typing e.g. 'C-x 8 RET GREEK TAB' completions are sorted in an
> non-alphabetical order:
>
> Ͳ GREEK CAPITAL LETTER ARCHAIC SAMPI
> Β GREEK CAPITAL LETTER BETA
> Χ GREEK CAPITAL LETTER CHI
> Ϯ GREEK CAPITAL LETTER DEI
> Δ GREEK CAPITAL LETTER DELTA
>
> where the 22nd letter of the Greek alphabet CHI is between BETA and DELTA.
> This is because currently completions are sorted by English names.
>
> The following patch sorts them by their Unicode order that mostly follows
> the alphabetical order, and at least makes more sense to be consistent
> with Unicode tables where characters are grouped more logically.
This has 2 disadvantages:
. the user needs to know the order of characters within a script
he/she doesn't necessarily read
. the user needs to know the order _between_ scripts, if the
candidates include characters from different Unicode blocks
If the user doesn't know this order, he/she might be unable to find
the required character quickly, if the list of candidates is long
enough.
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.
next prev parent reply other threads:[~2021-02-01 17:41 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 [this message]
2021-02-02 8:40 ` Lars Ingebrigtsen
2021-02-02 17:16 ` Juri Linkov
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
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=83wnvr65zg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46240@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).