From: Dmitry Gutov <dgutov@yandex.ru>
To: "João Távora" <joaotavora@gmail.com>, "Adam Porter" <adam@alphapapa.net>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Feedback on fido-mode
Date: Mon, 9 Mar 2020 16:50:20 +0200 [thread overview]
Message-ID: <eb5866ff-dc70-0590-4dcf-5dc9308d71f6@yandex.ru> (raw)
In-Reply-To: <CALDnm5121bVdTG6EEMoBEGm-vVfrnFLOXmhvuMSpeNrKCap3dQ@mail.gmail.com>
On 09.03.2020 16:42, João Távora wrote:
> Please be aware that fido-mode is really Icomplete-mode emulating _some_
> of ido-mode's features. It's likely that the emulation will get better
> in the future
> or even surpass ido-mode in features. But in any case, it's _not_ an
> emulation
> of Ivy-mode (if that's what you are after in some way).
I'm reasonably sure that more of these observations would apply to
ido-mode as well. Adam, have you tried it? Maybe with
ido-ubiquitous-mode (so it applies to all completing-read calls).
The difference vs. Ivy is about full flex (fuzzy) matching versus only
allowing arbitrary text where the search string has spaces. That's why
Ivy only matches the intended buffer for the input "init".
And fuzzy matching doesn't work as well when input strings are so long.
fido-mode could benefit from a possibility to choose a search style like
Ivy's, but first, I think, we should unbind SPC from
minibuffer-complete-word everywhere.
next prev parent reply other threads:[~2020-03-09 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 15:16 Feedback on fido-mode Adam Porter
2020-03-09 14:34 ` jixiuf
2020-03-09 14:42 ` João Távora
2020-03-09 14:50 ` Dmitry Gutov [this message]
2020-03-09 15:03 ` João Távora
2020-03-09 15:06 ` Dmitry Gutov
2020-03-09 15:08 ` João Távora
2020-03-09 15:59 ` Drew Adams
2020-03-09 17:12 ` Eli Zaretskii
2020-03-09 17:14 ` João Távora
2020-03-09 22:43 ` Dmitry Gutov
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=eb5866ff-dc70-0590-4dcf-5dc9308d71f6@yandex.ru \
--to=dgutov@yandex.ru \
--cc=adam@alphapapa.net \
--cc=emacs-devel@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 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).