From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Emacs completion matches selection UI Date: Mon, 23 Dec 2013 08:42:51 -0500 Message-ID: References: <87fvqtg02v.fsf@flea.lifelogs.com> <87haa8moh6.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 1387806188 4150 80.91.229.3 (23 Dec 2013 13:43:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 23 Dec 2013 13:43:08 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 23 14:43:13 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 1Vv5mq-0006kF-4K for ged-emacs-devel@m.gmane.org; Mon, 23 Dec 2013 14:43:12 +0100 Original-Received: from localhost ([::1]:33625 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vv5mp-0005LU-Ot for ged-emacs-devel@m.gmane.org; Mon, 23 Dec 2013 08:43:11 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41174) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vv5mg-0005G6-DA for emacs-devel@gnu.org; Mon, 23 Dec 2013 08:43:09 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vv5mY-0007WX-8l for emacs-devel@gnu.org; Mon, 23 Dec 2013 08:43:02 -0500 Original-Received: from pruche.dit.umontreal.ca ([132.204.246.22]:57054) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vv5mY-0007WK-1v for emacs-devel@gnu.org; Mon, 23 Dec 2013 08:42:54 -0500 Original-Received: from fmsmemgm.homelinux.net (lechon.iro.umontreal.ca [132.204.27.242]) by pruche.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id rBNDgoQH001441; Mon, 23 Dec 2013 08:42:51 -0500 Original-Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848) id 39C07AE21D; Mon, 23 Dec 2013 08:42:51 -0500 (EST) In-Reply-To: <87pponagzs.fsf@flea.lifelogs.com> (Ted Zlatanov's message of "Mon, 23 Dec 2013 07:28:39 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV4801=0 X-NAI-Spam-Version: 2.3.0.9362 : core <4801> : inlines <347> : streams <1095727> : uri <1632927> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.22 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:166770 Archived-At: > 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? The code which does not use minibuffer.el for its completion generally rolls its own. Grepping for *Completions* and display-completion-list is what I've done so far, but I probably missed some. I don't think it's terribly important to make sure we got 100% of the cases. > 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? 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'? Could be. Tho as mentioned before, I'm not sure that there's a need for caller-provided preferences. > I would like that, too, so choosing from a list of elements can use all > the improvements suggested here for `display-completion-list'. Not sure what you mean by that: minibuffer completion would presumably use the same completion mechanism as in-buffer completion (as is already the case, to a large extent), so completing-read would already use the new mechanisms. > Could this be a new `display-list' function, used to display both > completion selection (through `display-completion-list') and > list selection? Could be. I don't know enough in which contexts "list selection" could be used to know if/how it would make sense. Stefan