From: Manuel Uberti <manuel.uberti@inventati.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: 49888@debbugs.gnu.org
Subject: bug#49888: 28.0.50; fido-mode not sorting by recency
Date: Sun, 15 Aug 2021 10:34:19 +0200 [thread overview]
Message-ID: <5d2b912a-0056-cd96-009d-44b32594eafe@inventati.org> (raw)
In-Reply-To: <87bl5zxglw.fsf@gmail.com>
On 15/08/21 10:22, João Távora wrote:
> Thanks for the report. Seems like a nice reproduction recipe. But it
> seems like it demonstrates the problem for two fido-mode-using things,
> right? M-x _and_ C-x p p RET f, right? No problem, just checking.
Yes, both M-x and C-x p p RET f, but the same is true for C-x p f once I am in a
project. I used those two as examples because they are two of my most use
commands and, among those, the ones with usually more candidates than the rest.
I feel like recency could make a difference especially with commands like these
(i.e., commands with a lot of candidates) in terms of how quickly I can find
what I am looking for.
> Indeed, ido-mode was quited perfected in recency stuff. I was hard and
> still kind is to give up on its very nice default M-p binding that
> searches the recent history with whatever you have entered as a
> pattern. I used to use that all the time, and still haven't found a
> nice substitute in fido-mode or any other completer for that matter.
True, although I still find M-p useful in fido-mode especially in M-x when I
want to reach for the last or second-to-last command.
--
Manuel Uberti
www.manueluberti.eu
next prev parent reply other threads:[~2021-08-15 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 13:04 bug#49888: 28.0.50; fido-mode not sorting by recency Manuel Uberti
2021-08-15 8:22 ` João Távora
2021-08-15 8:34 ` Manuel Uberti [this message]
2021-08-15 12:11 ` João Távora
2021-08-15 12:19 ` João Távora
2021-08-15 12:38 ` João Távora
2021-08-15 13:49 ` Manuel Uberti
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d2b912a-0056-cd96-009d-44b32594eafe@inventati.org \
--to=manuel.uberti@inventati.org \
--cc=49888@debbugs.gnu.org \
--cc=joaotavora@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.