all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Why fido, icycles, ido, icomplete
Date: Wed, 6 Nov 2019 22:20:18 +0100	[thread overview]
Message-ID: <20191106212018.cnddqzlo5rpdhi6s@Ergus> (raw)
In-Reply-To: 20191106212018.cnddqzlo5rpdhi6s.ref@Ergus

Hi:

Sorry I have a sacrilegious question, maybe too obvious for everyone,
but not for me yet.

90% of the emacs users are actually using ivy or helm... The statistics
of downloaded packages are there; but also they are provided by default
as part of the most popular customizations like spacemacs.

Apart from that we actually already have (and invest effort supporting)
ido, icomplete and maybe others provided as internal packages... in
spite they are not (with huge difference) as popular as ivy or helm in
these days. And at least I don't know how to differentiate one from the
other.

So:

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?

2) Why we don't move all of those (the old and the new ones) to elpa as
independent packages? (this will help also to know their individual
popularity in our days and if it makes sense to invest more or less time
in each of them)

3) If ivy & helm are the most popular these days... why we don't try to
collaborate a bit more with their maintainers in order to provide them
functionalities that they are emulating now with hacks? It will be more
efficient now and beneficial for future similar packages in the future.






       reply	other threads:[~2019-11-06 21:20 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 ` Ergus [this message]
2019-11-06 21:30   ` Why fido, icycles, ido, icomplete 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
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=20191106212018.cnddqzlo5rpdhi6s@Ergus \
    --to=spacibba@aol.com \
    --cc=drew.adams@oracle.com \
    --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.