From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: Emacs completion matches selection UI Date: Mon, 06 Jan 2014 18:21:13 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <8761pwg0ie.fsf@flea.lifelogs.com> References: <20131231155235.GA9294@c3po> <878uuxhs5s.fsf@flea.lifelogs.com> <87txdkcdb6.fsf@gmail.com> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1389050392 7228 80.91.229.3 (6 Jan 2014 23:19:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 6 Jan 2014 23:19:52 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 07 00:19:59 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1W0JSg-0007wc-7l for ged-emacs-devel@m.gmane.org; Tue, 07 Jan 2014 00:19:58 +0100 Original-Received: from localhost ([::1]:38056 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0JSf-00018K-P3 for ged-emacs-devel@m.gmane.org; Mon, 06 Jan 2014 18:19:57 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41088) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0JSW-00012B-VN for emacs-devel@gnu.org; Mon, 06 Jan 2014 18:19:54 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W0JSR-00066q-LX for emacs-devel@gnu.org; Mon, 06 Jan 2014 18:19:48 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:45319) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0JSR-00066k-FO for emacs-devel@gnu.org; Mon, 06 Jan 2014 18:19:43 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1W0JSP-0007Sw-Sf for emacs-devel@gnu.org; Tue, 07 Jan 2014 00:19:41 +0100 Original-Received: from c-98-229-61-72.hsd1.ma.comcast.net ([98.229.61.72]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 07 Jan 2014 00:19:41 +0100 Original-Received: from tzz by c-98-229-61-72.hsd1.ma.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 07 Jan 2014 00:19:41 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 52 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-98-229-61-72.hsd1.ma.comcast.net X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:rSnHevQsOqDqtk/dsztIJ9FWv3s= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:167541 Archived-At: On Sat, 04 Jan 2014 09:21:33 +0000 joaotavora@gmail.com (João Távora) wrote: JT> Ted Zlatanov writes: >> Based on the discussion so far, it seems that: >> >> [...] >> - it should be possible to implement a generic frontend for completion >> that both can use, and other tools like yasnippet can use IIUC. The JT> Thanks for the summary of the discussion so far, but this last statement JT> might bring some confusion... Yasnippet can curiously fit into many JT> parts of the problem: JT> * It can be a source to completion frameworks, auto-complete and company JT> have such sources. Right. A "completion backend" I think is the current term. JT> * It prompts the user when it finds more than one snippet for an abbrev, JT> and uses its own `yas-prompt-functions' abstraction. Some of the JT> functions offer completion. This is a "completion frontend" IIUC. yasnippet.el can have its own prompt functions if they work with the larger completion API (as followup queries), otherwise it's probably best to avoid integrating Yasnippet as I described. JT> * It installs a keybinding for TAB which is problematic because it is JT> very sought-after binding for completion-related stuff. The parts of JT> this discussion that concerned yasnippet dealed with this, AFAIK. Yes, this is a fun debate. I'd like to leave it up to the user and make the default conservative, but it should be context-dependent and easy to augment by a package like Yasnippet, IMHO. >> with their experience of writing it once already, and we have to make >> sure we don't end up with a solution no one wants to use :) JT> Yep. For me personally it would make sense to evaluate alternatives JT> based a matrix like the one proposed by Stefan earlier: JT> http://article.gmane.org/gmane.emacs.devel/166661/match=completion+ui OK, but I don't think a matrix can cover all the subtleties. I think fitting Emacs' current completion cases, company-mode, and completion-ui+Predictive into a single framework would be a good start and then you can see if Yasnippet can fit there. Maybe it can't without a complete refit, and in that case we leave it alone. (I think Helm will also be in this category, its UI is too integrated and is not really a completion framework in the traditional sense.) Ted