From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.devel Subject: Re: elpa.gnu.org packages requiring external packages Date: Tue, 06 Feb 2018 11:45:29 -0800 Message-ID: <87fu6daome.fsf@ericabrahamsen.net> References: <87inbjo1y8.fsf@ericabrahamsen.net> <87h8r1lxy8.fsf@ericabrahamsen.net> <87y3kcfveg.fsf@ericabrahamsen.net> <87y3ka6gxx.fsf@ericabrahamsen.net> <3adfa163-3238-09a0-a345-205babcfe9ef@yandex.ru> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1517948652 31851 195.159.176.226 (6 Feb 2018 20:24:12 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 6 Feb 2018 20:24:12 +0000 (UTC) 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 Tue Feb 06 21:24:08 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ej9mL-0006cc-BT for ged-emacs-devel@m.gmane.org; Tue, 06 Feb 2018 21:23:45 +0100 Original-Received: from localhost ([::1]:57083 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ej9oM-0001YU-Kj for ged-emacs-devel@m.gmane.org; Tue, 06 Feb 2018 15:25:50 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54360) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ej9Bj-0006yv-BW for emacs-devel@gnu.org; Tue, 06 Feb 2018 14:45:56 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ej9Bg-0000xY-57 for emacs-devel@gnu.org; Tue, 06 Feb 2018 14:45:55 -0500 Original-Received: from [195.159.176.226] (port=35753 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ej9Bf-0000xG-TR for emacs-devel@gnu.org; Tue, 06 Feb 2018 14:45:52 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1ej99R-0002Zq-9Q for emacs-devel@gnu.org; Tue, 06 Feb 2018 20:43:33 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 42 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:rt2sKcOF/V1koUJiQoUvIFZGTyI= 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.21 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:222586 Archived-At: Dmitry Gutov writes: > On 2/3/18 03:43, Eric Abrahamsen wrote: > >> company primarily does popup-on-a-timer; > > popup-on-a-timer is irrelevant. company supports > completion-at-point-functions via company-capf. > > The only major feature that completion-at-point-functions don't get > (that company backends do) is asynchronous operation. > >> I think calling it as an >> explicit completion command (while supported) isn't how it's expected >> to be used. > > M-x company- is a well-established way of using it (not the > most popular one, of course). > >>> And overall, I really wish someone could sit down, take the ivy, >>> company, helm, and completion-at-point-function APIs and design a new >>> API which can be used by all of those UIs so you don't have to implement >>> N different slight variations of the same thing. > > It would be nice to see some input from Ivy's author: it does support > asynchronous operation, and even operating on an incomplete set of > results. That's something CAPF does not have yet. Add fuzzy matching, > and that's basically everything we want such API to have. > >> But they do their things in such different ways. Some work on a timer >> with a popup (company), others tie into the existing completion >> mechanisms (helm and ivy), and others provide their own versions of >> basic Emacs commands (helm and counsel). How much unification is >> possible? > > company-capf is an example of one such unification. And given a > powerful-enough API, all packages could have the ability, at least, to > switch to it. I think I came off more skeptical than I meant to here. I really was just curious how this would work. It's not an area of Emacs I've spent much time with (and am not likely to).