unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: Jakub Jankiewicz <jcubic@onet.pl>,
	Lars Ingebrigtsen <larsi@gnus.org>,
	12490@debbugs.gnu.org
Subject: bug#12490: 24.2; Search inside Minibuffer don't work with M-x (M-x C-s)
Date: Mon, 02 Dec 2019 00:38:22 +0200	[thread overview]
Message-ID: <87o8wrisdd.fsf@mail.linkov.net> (raw)
In-Reply-To: <CADwFkmnsgxbbsjhWACt5vQGoynyO4u0v3gF6sVqQgAjN4GK5BQ@mail.gmail.com> (Stefan Kangas's message of "Sun, 1 Dec 2019 08:36:59 +0100")

>> The problem why this patch is not installed is the need to decide
>> in what order to sort these commands.  The patch sorts alphabetically,
>> but maybe better to sort by command usage frequency, or somesuch.
>
> One possibility would be to install it and improve the ordering later.

I agree.

> BTW, do we have a mechanism for sorting by command frequency?

One possibility is to use the minibuffer history to sort by the number
of occurrences of each history element, but this method doesn't work
when history-delete-duplicates is customized to non-nil, so there are
no duplicates in the history.

Although I noticed that icomplete.el often proposes the most
relevant elements first, but I never investigated how it does this,
maybe by frequency?





  reply	other threads:[~2019-12-01 22:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-22 20:42 bug#12490: 24.2; Search inside Minibuffer don't work with M-x (M-x C-s) Jakub Jankiewicz
2012-09-22 23:21 ` Juri Linkov
2012-09-23  9:27   ` Jakub Jankiewicz
2019-10-30 22:25   ` Stefan Kangas
2019-11-23 14:41     ` Lars Ingebrigtsen
2019-11-30 21:43       ` Juri Linkov
2019-11-30 23:41         ` Drew Adams
2019-12-01  7:36         ` Stefan Kangas
2019-12-01 22:38           ` Juri Linkov [this message]
2019-12-02 22:51             ` Juri Linkov
2020-08-19 13:52             ` Lars Ingebrigtsen

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=87o8wrisdd.fsf@mail.linkov.net \
    --to=juri@jurta.org \
    --cc=12490@debbugs.gnu.org \
    --cc=jcubic@onet.pl \
    --cc=larsi@gnus.org \
    --cc=stefan@marxist.se \
    /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).