From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel,gmane.emacs.helm.user Subject: Re: Emacs completion matches selection UI Date: Mon, 23 Dec 2013 09:52:40 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <871u13aabr.fsf@flea.lifelogs.com> References: <87fvqtg02v.fsf@flea.lifelogs.com> <874n67n450.fsf@flea.lifelogs.com> <87eh5bkxca.fsf@flea.lifelogs.com> <87d2kuzzqj.fsf@uwakimon.sk.tsukuba.ac.jp> <87a9fylusq.fsf@flea.lifelogs.com> <878uvizrwz.fsf@uwakimon.sk.tsukuba.ac.jp> <8761qmkyn1.fsf@flea.lifelogs.com> <87zjnyxdpb.fsf@uwakimon.sk.tsukuba.ac.jp> <87k3f2j7xv.fsf@flea.lifelogs.com> <2518D79A-B9E4-45DF-A403-8330145DFD17@gmail.com> <87eh58j0x3.fsf@flea.lifelogs.com> <87mwjvfrfy.fsf@flea.lifelogs.com> <877gawbhp0.fsf@flea.lifelogs.com> <87pponagzs.fsf@flea.lifelogs.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1387810314 19219 80.91.229.3 (23 Dec 2013 14:51:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 23 Dec 2013 14:51:54 +0000 (UTC) Cc: emacs-helm@googlegroups.com To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 23 15:51:59 2013 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 1Vv6rN-0005X6-Ri for ged-emacs-devel@m.gmane.org; Mon, 23 Dec 2013 15:51:58 +0100 Original-Received: from localhost ([::1]:33967 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vv6rN-0001EE-IL for ged-emacs-devel@m.gmane.org; Mon, 23 Dec 2013 09:51:57 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54668) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vv6r4-0000tb-Gf for emacs-devel@gnu.org; Mon, 23 Dec 2013 09:51:43 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vv6qz-0001g4-5c for emacs-devel@gnu.org; Mon, 23 Dec 2013 09:51:38 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:55025) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vv6qy-0001g0-V7 for emacs-devel@gnu.org; Mon, 23 Dec 2013 09:51:33 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Vv6qw-0005A9-M9 for emacs-devel@gnu.org; Mon, 23 Dec 2013 15:51:30 +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 ; Mon, 23 Dec 2013 15:51:30 +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 ; Mon, 23 Dec 2013 15:51:30 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 47 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" User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:jYM9kv6OqM6FBUSAq8taW2HpmDQ= 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:166778 gmane.emacs.helm.user:535 Archived-At: On Mon, 23 Dec 2013 08:42:51 -0500 Stefan Monnier wrote: >> OK, is there a way to make a verification and testing plan for this? If >> there was some automation around completion support, it would certainly >> speed things up, but we need at least a list of currently non-compliant >> modes in Emacs. How do you look for the exceptions, by searching for >> old functions or testing manually? SM> The code which does not use minibuffer.el for its completion generally SM> rolls its own. Grepping for *Completions* and display-completion-list is SM> what I've done so far, but I probably missed some. SM> I don't think it's terribly important to make sure we got 100% of the cases. OK, I'll move on. If the new UI proves compelling, users will tell us they want it supported in their favorite modes :) >> As with company-mode, this can be a frontend choice (affecting >> `display-completion-list', and see below for the suggested >> `display-list' function). How about a defcustom >> `completion-ui-frontend' with some choices? SM> The general idea of completion-ui was great, yes. >> For the user, a new defcustom `completion-ui-preferences'? And for the >> caller, some kind of plist/alist passed to `completion-at-point' that >> merges cleanly with `completion-ui-preferences'? SM> Could be. Tho as mentioned before, I'm not sure that there's a need for SM> caller-provided preferences. OK, I'll work on this off-list to keep the noise down, I've generated enough emacs-devel traffic so far! Dmitry, Stephen, please let me know directly if you want to participate in the design of `completion-ui-*' as described here. I honestly can't keep track of all the completion packages available, but I'm xposting/CC-ing the Helm developers, and Toby Cubitt (because of http://www.emacswiki.org/emacs/CompletionUI the prefix "completion-ui" may need to be changed, but it seems to have similar ideas to the frontends we're describing here). Drew Adams (Icicles) and Kim Storm (ido) may also be interested but I think they read emacs-devel. For all the autocomplete forks and add-ons, I have no idea who to CC. Anyhow, if you're interested, reply to me directly please. Thanks Ted