GNU bug report logs - #5139
23.1.50; feature request: completion-buffer-sort-function

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 5139 in the body.
You can then email your comments to 5139 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: "Roland Winkler" <Roland.Winkler <at> physik.uni-erlangen.de>
To: emacs-pretest-bug <at> gnu.org
Subject: 23.1.50; feature request: completion-buffer-sort-function
Date: Sun, 06 Dec 2009 21:21:36 -0600

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.

Kind of related:

Such a function could do more than sorting the completions (or being
a sort predicate). It could also help formatting the *Completions*
buffer. Say, a *Completions* buffer can be hard to read when it
contains many entries. If it lists, for example, buffer names, it
could sort the buffer names by mode and put some kind of seperator
between groups of buffers with the same mode. Then this seperator
could be translated into something like an empty line in the
*Completions* buffer.

Roland

Message #10 received at 5139 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: "Roland Winkler" <Roland.Winkler <at> physik.uni-erlangen.de>
Cc: 5139 <at> debbugs.gnu.org
Subject: Re: bug#5139: 23.1.50; feature request:
 completion-buffer-sort-function
Date: Tue, 01 Oct 2019 16:58:28 +0200

"Roland Winkler" <Roland.Winkler <at> physik.uni-erlangen.de> writes:

> 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".

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #17 received at 5139 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>, Roland Winkler
 <Roland.Winkler <at> physik.uni-erlangen.de>
Cc: 5139 <at> debbugs.gnu.org
Subject: RE: bug#5139: 23.1.50; feature request:
 completion-buffer-sort-function
Date: Tue, 1 Oct 2019 09:53:49 -0700 (PDT)

> > 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.