From: Eli Zaretskii <eliz@gnu.org>
To: Protesilaos Stavrou <info@protesilaos.com>
Cc: 53362@debbugs.gnu.org
Subject: bug#53362: 29.0.50; [PATCH] Make Completions sorting a user option
Date: Wed, 19 Jan 2022 15:27:38 +0200 [thread overview]
Message-ID: <83k0evsvn9.fsf@gnu.org> (raw)
In-Reply-To: <87bl07lvae.fsf@protesilaos.com> (message from Protesilaos Stavrou on Wed, 19 Jan 2022 15:17:13 +0200)
> From: Protesilaos Stavrou <info@protesilaos.com>
> Cc: 53362@debbugs.gnu.org
> Date: Wed, 19 Jan 2022 15:17:13 +0200
>
> >> +(defcustom completions-sort 'lexicographic
> >> + "Sort candidates in the *Completions* buffer.
> >> +
> >> +The value can be nil to disable sorting altogether,
> >> +`alphabetical' for alphabetical sorting, `lexicographic' for
> >> +lexicographic sorting
> >
> > Here you expect everyone to understand the subtle difference between
> > these two sorting orders. I don't think this expectation is
> > reasonable.
>
> Perhaps it is better to reference string-lessp and string-version-lessp
> directly?
That'd be a step backward, IMO.
> > Doesn't string-version-lessp do stuff that is only appropriate with
> > version numbers like 1.2.3beta?
>
> It also helps when the string starts with a number:
>
> (sort '("1 test" "21 test" "11 test" "2 test") #'string-lessp)
> ;; => ("1 test" "11 test" "2 test" "21 test")
Yes, and how does that match the "alphabetical order" description?
next prev parent reply other threads:[~2022-01-19 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 12:26 bug#53362: 29.0.50; [PATCH] Make Completions sorting a user option Protesilaos Stavrou
2022-01-19 12:56 ` Eli Zaretskii
2022-01-19 13:17 ` Protesilaos Stavrou
2022-01-19 13:27 ` Eli Zaretskii [this message]
2022-01-19 14:09 ` Protesilaos Stavrou
2022-01-19 17:16 ` Protesilaos Stavrou
2022-01-20 5:33 ` Protesilaos Stavrou
2022-01-24 13:37 ` Eli Zaretskii
2022-01-19 16:10 ` bug#53362: [External] : " 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=83k0evsvn9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53362@debbugs.gnu.org \
--cc=info@protesilaos.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).