From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Why fido, icycles, ido, icomplete Date: Wed, 06 Nov 2019 23:39:07 +0100 Message-ID: <87o8xoeik4.fsf@telefonica.net> References: <20191106212018.cnddqzlo5rpdhi6s.ref@Ergus> <20191106212018.cnddqzlo5rpdhi6s@Ergus> <877e4c1x3r.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="89511"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 06 23:39:27 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iSTxX-000N6y-At for ged-emacs-devel@m.gmane.org; Wed, 06 Nov 2019 23:39:27 +0100 Original-Received: from localhost ([::1]:35838 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iSTxV-0007XI-Qd for ged-emacs-devel@m.gmane.org; Wed, 06 Nov 2019 17:39:25 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35296) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iSTxP-0007Wy-1c for emacs-devel@gnu.org; Wed, 06 Nov 2019 17:39:19 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iSTxO-0006ph-0N for emacs-devel@gnu.org; Wed, 06 Nov 2019 17:39:18 -0500 Original-Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:53988 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iSTxN-0006oH-Pr for emacs-devel@gnu.org; Wed, 06 Nov 2019 17:39:17 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1iSTxK-000Myu-Iv for emacs-devel@gnu.org; Wed, 06 Nov 2019 23:39:14 +0100 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:/RdPJAM4WGha9oUOSy/EiE1wvK0= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:241883 Archived-At: João Távora writes: > Now, I wish I could just put 'flex' (and many other things) in > ido-mode. Ido has a `flex' completion style. Maybe it is a different one? > 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 ). Should it? This is like the recent discussion about implementing new commands on VC: insisting on a common interface hampers diversity and innovation. We must accept that different tools sometimes deserve specific user interfaces. > This > means it doesn't work nicely for M-x, C-h f, and many many other > completion situations. Ido works nicely here for those cases with just a few lines on my .emacs and an extra package installed (ido-hacks). [snip] > 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. Ido here has a customized look (courtesy of ido-grid-mode.el), a customized completion scheme (flx-ido) and some more bells and whistles. This indicates to me that ido is more hackable than your message implies. I'm not denying that it could be much better on that regard, though. [snip]