From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: propose adding Icicles to Emacs Date: Sat, 16 Jun 2007 14:51:15 -0400 Message-ID: References: Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1182020263 10706 80.91.229.12 (16 Jun 2007 18:57:43 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 16 Jun 2007 18:57:43 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 16 20:57:41 2007 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 1HzdSr-000751-Hm for ged-emacs-devel@m.gmane.org; Sat, 16 Jun 2007 20:57:37 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HzdSq-0004w0-TW for ged-emacs-devel@m.gmane.org; Sat, 16 Jun 2007 14:57:36 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HzdMk-0000q3-15 for emacs-devel@gnu.org; Sat, 16 Jun 2007 14:51:18 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HzdMi-0000p2-Uw for emacs-devel@gnu.org; Sat, 16 Jun 2007 14:51:17 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HzdMi-0000og-Mz for emacs-devel@gnu.org; Sat, 16 Jun 2007 14:51:16 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HzdMi-0006Pb-BC for emacs-devel@gnu.org; Sat, 16 Jun 2007 14:51:16 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1HzdMh-0006xH-PR; Sat, 16 Jun 2007 14:51:15 -0400 In-reply-to: X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) 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:73092 Archived-At: Specific example: Some users like buffer-name completion to always be strict, a la Ibuffer, rather than lax, a la `switch-to-buffer'. Icicles has a user option that you can set to make REQUIRE-MATCH effectively strict for Icicles commands that use buffer names. Those buffer commands bind variable `icicle-require-match-flag' to the user's choice (which is the value of `icicle-buffer-require-match-flag'. My `completing-read' checks `icicle-require-match-flag' and overrides the REQUIRE-MATCH arg if appropriate. I mention buffer-name completion because it is a common example, but the same principle applies to any completion. If we want such a feature, it should be a separate feature. Please see my reply to one of Stefan's emails on this topic. I am repeating myself. Anyway... 1. `M-*' (`icicle-narrow-candidates') calls `completing-read' or `read-file-name' again, recursively, to match an additional pattern you provide. I call this "progressive completion", and it is akin to piping greps. In this recursive call, the same value of REQUIRE-MATCH should be used. Since this is in a different command, I need a global variable for this value. I don't mind adding `minibuffer-completion-require-match' if we end up needing it. 2. Also, `icicle-candidate-action', which is `C-RET' (likewise, the alternative-action command, bound to `C-S-RET'), uses the recorded value of REQUIRE-MATCH to handle the action. When a match is required, the candidate must be one of those in `minibuffer-completion-table'. For lax completion, `C-RET' lets you act on any input you type. If we implement this whole feature as I suggested, it will do the right thing with REQUIRE-MATCH automatically.