From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Francois Fleuret Newsgroups: gmane.emacs.devel Subject: Re: A dynamic pattern-matching Date: Tue, 3 Mar 2009 22:33:35 +0100 Message-ID: <18861.41519.484433.255547@moose.fleuret.org> References: <18860.59659.494547.384677@moose.fleuret.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1236138879 14176 80.91.229.12 (4 Mar 2009 03:54:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 4 Mar 2009 03:54:39 +0000 (UTC) Cc: emacs-devel@gnu.org, Francois Fleuret To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 04 04:55:55 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LeiD4-0006Gu-VD for ged-emacs-devel@m.gmane.org; Wed, 04 Mar 2009 04:55:55 +0100 Original-Received: from localhost ([127.0.0.1]:53629 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LeiBj-0005jW-T0 for ged-emacs-devel@m.gmane.org; Tue, 03 Mar 2009 22:54:31 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LecFI-00087J-4t for emacs-devel@gnu.org; Tue, 03 Mar 2009 16:33:48 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LecFG-000877-Ib for emacs-devel@gnu.org; Tue, 03 Mar 2009 16:33:46 -0500 Original-Received: from [199.232.76.173] (port=37489 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LecFG-000874-CK for emacs-devel@gnu.org; Tue, 03 Mar 2009 16:33:46 -0500 Original-Received: from barracuda.idiap.ch ([192.33.221.13]:40131) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LecFF-0003Yu-OG for emacs-devel@gnu.org; Tue, 03 Mar 2009 16:33:46 -0500 X-ASG-Debug-ID: 1236116022-1641001d0000-uRBjzT X-Barracuda-URL: http://barracuda.idiap.ch:8000/cgi-bin/mark.cgi Original-Received: from mail02.vs.idiap.ch (localhost [127.0.0.1]) by barracuda.idiap.ch (Spam Firewall) with ESMTP id 8FD398628E; Tue, 3 Mar 2009 22:33:42 +0100 (CET) Original-Received: from mail02.vs.idiap.ch (mail02.vs.idiap.ch [172.17.90.82]) by barracuda.idiap.ch with ESMTP id Hld3fwE42vEEFsxz (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO); Tue, 03 Mar 2009 22:33:42 +0100 (CET) X-ASG-Whitelist: Client Original-Received: from idiap.ch (235-53.3-85.cust.bluewin.ch [85.3.53.235]) (using SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail02.vs.idiap.ch (Postfix) with ESMTPSA id 71B188112; Tue, 3 Mar 2009 22:33:42 +0100 (CET) Original-Received: by idiap.ch (Postfix, from userid 1000) id 7A7B18BC048; Tue, 3 Mar 2009 22:33:35 +0100 (CET) X-ASG-Orig-Subj: Re: A dynamic pattern-matching X-Mailer: VM 8.0.9 under Emacs 23.0.90.1 (i686-pc-linux-gnu) X-Barracuda-Connect: mail02.vs.idiap.ch[172.17.90.82] X-Barracuda-Start-Time: 1236116022 X-Barracuda-Encrypted: AES256-SHA X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at idiap.ch X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-Mailman-Approved-At: Tue, 03 Mar 2009 22:54:28 -0500 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:109431 Archived-At: Hi Stefan, > - it'd be easy to write a variant of icomplete-mode that addresses > point 1 by using a separate buffer (which we'd call > "*Completions*"). Well, that's not clear to me. IIUC completing-read and other functions of that kind blocks the calling program until the user makes up his mind, while my selector/select uses a callback. In fact, is it really desirable to use that selector in place of the standard completion functions ? My idea was more to provide an alternative to recentf-open-files and switch-buffer. > - I guess point 2 is also somewhat secondary, tho it's important to > have a notion of "the currently selected entry" (this is also > used in ido/ibuffer and is somewhat missing in the default > completion code) In fact, I always considered using a "real buffer" to be a major (good) thing, but now that you talk about it I wonder why, since what one usually does in the selector buffer is not interrupted by something else. Now I presume it's a question of habit, but I never felt really at home in the minibuffer ... > - I don't think point 3 is important, right? Nope, it's not > - point 4 can be simulated by adding a "*" at the beginning of > the pattern. Or we could add a `substring' completion-style. Yes. But I would vote for having a variable that specifies how the typed pattern has to be interpreted { substrings, regexp, leadingstring } or something. > - point 5 hopefully can be implemented as a completion-style. Not sure to understand what you do mean here. > - point 6... not sure: it seems like the difference might be important, > along with the fact that the user may like to use this style of > selection for some commands but not all. See my comment about the 1/ Regards, -- Francois Fleuret http://www.idiap.ch/~fleuret/