all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Ergus <spacibba@aol.com>
Cc: Drew Adams <drew.adams@oracle.com>, emacs-devel@gnu.org
Subject: Re: Why fido, icycles, ido, icomplete
Date: Wed, 06 Nov 2019 22:03:20 +0000	[thread overview]
Message-ID: <877e4c1x3r.fsf@gmail.com> (raw)
In-Reply-To: <20191106212018.cnddqzlo5rpdhi6s@Ergus> (Ergus's message of "Wed,  6 Nov 2019 22:20:18 +0100")

Ergus <spacibba@aol.com> writes:

> 1) Do we really need another confusing mode (fido-mode)? instead of
> improve one of the already existing alternatives with just an option to
> use flex?

I'm sorry you find the name confusing.  I find it appealing (it's "fake
ido"), but we can change it (Stefan proposed icomplete-ido-mode).

Now, I wish I could just put 'flex' (and many other things) in ido-mode.
Actually the matter is much more complicated.  Ido mode is a completely
separate completion system that doesn't respect Emacs completion
interfaces (completion-in-region-functions,
completion-at-point-functions, completion-styles, etc etc etc ).  This
means it doesn't work nicely for M-x, C-h f, and many many other
completion situations.  So, believe me, I tried to change it... and gave
up immediately (but go ahead, open lisp/ido.el hehehe).

Recently, we worked together with the Helm developer to help Helm to
abide by a greater number of Emacs completion interfaces.  It should
have, among other benefits, the interesting result that you can use Helm
matching styles in icomplete.el's frontend.  Or company's.  Or Emacs's
flex in Helm.  So I don't think it's true there's no cooperation.

Maybe you can convince someone to do that for ido.el, idk.

I was a heavy Ido addict for many years because it has the best
interface, hands down, much better than Ivy, or Helm, IMO of course.  I
also know many people in my company that swear by it.  But the
implementation was impossibly hard to hack on.  Then I found
icomplete.el, with very lean implementation (around 8x less lines) and
the closest gap to ido-mode.  I improved a decent part of icomplete.el,
so Icomplete mode is now better by itself.  But that gap to ido-mode is
still annoyingly (and legitimately) there, and we can't just change
icomplete-mode's defaults like that.

So fido-mode.  It's really just icomplete with slightly different
defaults that emulate ido mode as close as possible.  Indeed the
specific contract of fido-mode is to emulate ido-mode as much as
possible, to use it as a reference, so if you find something in the
emulation that can be improved, please share.

Regarding your other points, <shrug> that's just the way Emacs is.  I
like lean implementations that play along with the rest of Emacs, so I
chose icomplete.el to use and to hack on.

João






  parent reply	other threads:[~2019-11-06 22:03 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191106212018.cnddqzlo5rpdhi6s.ref@Ergus>
2019-11-06 21:20 ` Why fido, icycles, ido, icomplete Ergus
2019-11-06 21:30   ` Daniele Nicolodi
2019-11-06 22:27     ` Ergus
2019-11-06 22:03   ` João Távora [this message]
2019-11-06 22:39     ` Óscar Fuentes
2019-11-06 22:57       ` João Távora
2019-11-06 23:07         ` Óscar Fuentes
2019-11-07  0:36           ` João Távora
2019-11-07  1:07             ` Óscar Fuentes
2019-11-07  1:21               ` Ergus
2019-11-07  1:51                 ` Óscar Fuentes
2019-11-07 10:09               ` João Távora
2019-11-07 18:50                 ` Óscar Fuentes
2019-11-06 23:21     ` Ergus
2019-11-06 23:59       ` Óscar Fuentes
2019-11-07  0:47         ` Ergus
2019-11-07  2:20           ` Óscar Fuentes
2019-11-07  4:59             ` Ergus
2019-11-07 18:26               ` Óscar Fuentes
2019-11-07 14:09             ` Stefan Monnier
2019-11-07 20:35               ` Óscar Fuentes
2019-11-07 21:11                 ` Stefan Monnier
2019-11-07 22:18                   ` Óscar Fuentes
2019-11-07 22:30                     ` Stefan Monnier
2019-11-07 22:34                     ` João Távora
2019-11-07  0:27       ` João Távora
2019-11-07  1:09         ` Ergus
2019-11-07 10:39           ` João Távora
2019-11-07 15:00             ` Ergus
2019-11-08 17:54     ` Filipp Gunbin
2019-11-08 18:10       ` Óscar Fuentes
2019-11-08 18:45       ` Nicolas Semrau
2019-11-08 19:12       ` Eli Zaretskii
2019-11-08 21:31         ` Juanma Barranquero
2019-11-08 22:54           ` João Távora
2019-11-08 23:11             ` Ergus

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=877e4c1x3r.fsf@gmail.com \
    --to=joaotavora@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=spacibba@aol.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.