From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Roland Winkler <Roland.Winkler@physik.uni-erlangen.de>
Cc: 5139@debbugs.gnu.org
Subject: bug#5139: 23.1.50; feature request: completion-buffer-sort-function
Date: Tue, 1 Oct 2019 09:53:49 -0700 (PDT) [thread overview]
Message-ID: <c0a13d36-d006-4828-a4cf-8412978df90b@default> (raw)
In-Reply-To: <87r23w4inf.fsf@gnus.org>
> > When a *Completions* buffer is generated by minibuffer-completion-help
> > it will sort the possible completions using string-lessp. It would be
> > nice if the sorting order was not hard-coded but could be modified
> > according to context. That's why I want to suggest to replace the
> > call of string-lessp by something like
> >
> > (funcall completion-buffer-sort-function)
> >
> > so that completion-buffer-sort-function can be bound by the caller
> > to something else according to context.
>
> I think what the various packages that do completion (ido, helm,
> company, etc) do is replace the entire completion function, which seems
> more flexible. And making all those respect such a variable I thing
> would be difficult.
>
> So I'm closing this as a "wontfix".
FWIW, Icicles does not hard-code the sort function,
including not doing so in any particular command.
(So it does not "replace the entire completion
function" with another one that hard-codes a
different sort function.)
It lets user change the sort order on the fly
during completion. And it lets users define and
control the available sort functions, in general
and per command.
https://www.emacswiki.org/emacs/Icicles_-_Sorting_Candidates
prev parent reply other threads:[~2019-10-01 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 3:21 bug#5139: 23.1.50; feature request: completion-buffer-sort-function Roland Winkler
2019-10-01 14:58 ` Lars Ingebrigtsen
2019-10-01 16:53 ` Drew Adams [this message]
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=c0a13d36-d006-4828-a4cf-8412978df90b@default \
--to=drew.adams@oracle.com \
--cc=5139@debbugs.gnu.org \
--cc=Roland.Winkler@physik.uni-erlangen.de \
--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).