unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Fri, 05 Feb 2021 00:34:17 +0200	[thread overview]
Message-ID: <87pn1fo42e.fsf@mail.linkov.net> (raw)
In-Reply-To: <87h7mrq002.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 04 Feb 2021 17:19:09 +0100")

>> Oops, I noticed that my previous implementation sorted by names
>> inside each block, not by code.  I'm not sure if this makes sense?
>> Definitely, sorting by code inside blocks should be implemented
>> as the primary feature, but should an additional option with previous
>> implementation be retained to sort inside blocks by names too?
>
> Having the option to sort by names within each block sounds nice to me.

Oh, then sorting order of sections would need own option.  Currently
sections are sorted by section names (i.e. mostly by script names
alphabetically, e.g. "adlam", "aegean-number", "ahom", etc.),
but a new option could sort them by their boundary codepoints
(i.e. "basic-latin", "latin-supplement", "latin-extended"),
so now options are going out of control :)





  reply	other threads:[~2021-02-04 22:34 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
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 [this message]
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=87pn1fo42e.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 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).