From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Why fido, icycles, ido, icomplete
Date: Thu, 07 Nov 2019 00:59:13 +0100 [thread overview]
Message-ID: <87ftj0eeum.fsf@telefonica.net> (raw)
In-Reply-To: 20191106232153.bb756hrf4ctwegkp@Ergus
Ergus <spacibba@aol.com> writes:
> I actually have very strong feelings behind ido in 2019 (I know I am a
> sort of apostate for this). But I think it is something that needs to be
> removed/deprecated/substituted for the good of newer alternatives like
> icomplete. So new users will try more maintained/ modern/ powerful/
> better integrated alternatives: like icomplete/ivy/helm.
Ido is not used by default. What good does to remove it?
> The intention is to move the users to the newer functionalities so they
> can get the best possible first impression.
New users are not exposed to ido at all. So I don't get your point.
> From the software point of view it is "complex" to keep such a big piece
> of code that nobody wants to touch anymore... specially if we already
> have alternatives for it.
People are not forced to work on Ido. They do because they want.
> I think Abo-abo actually tried to modify ido to improve it and he
> finally ended implementing ivy... was easier that way.
I tried Ivy and decided that it is clearly inferior to my ido config.
YMMV.
Can we stop prentending there is One True Way of doing things?
next prev parent reply other threads:[~2019-11-06 23:59 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
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 [this message]
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=87ftj0eeum.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=emacs-devel@gnu.org \
/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.