From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.bugs Subject: RE: Insufficient documentation on *how* to change SPC behaviour inminibuffer Date: Fri, 6 Jul 2007 11:26:07 -0700 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1183746402 8287 80.91.229.12 (6 Jul 2007 18:26:42 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 6 Jul 2007 18:26:42 +0000 (UTC) To: Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Jul 06 20:26:41 2007 connect(): Connection refused Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1I6sVs-0002sI-TZ for geb-bug-gnu-emacs@m.gmane.org; Fri, 06 Jul 2007 20:26:41 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I6sVs-0007w3-6a for geb-bug-gnu-emacs@m.gmane.org; Fri, 06 Jul 2007 14:26:40 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I6sVp-0007vl-Pi for bug-gnu-emacs@gnu.org; Fri, 06 Jul 2007 14:26:37 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I6sVm-0007uH-5S for bug-gnu-emacs@gnu.org; Fri, 06 Jul 2007 14:26:36 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I6sVl-0007uE-TU for bug-gnu-emacs@gnu.org; Fri, 06 Jul 2007 14:26:33 -0400 Original-Received: from agminet01.oracle.com ([141.146.126.228]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1I6sVl-0006XL-FG for bug-gnu-emacs@gnu.org; Fri, 06 Jul 2007 14:26:33 -0400 Original-Received: from rgmgw1.us.oracle.com (rgmgw1.us.oracle.com [138.1.186.110]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id l66IQUqM016480 for ; Fri, 6 Jul 2007 13:26:30 -0500 Original-Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by rgmgw1.us.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id l66GWRKe030474 for ; Fri, 6 Jul 2007 12:26:29 -0600 Original-Received: from dhcp-amer-csvpn-gw2-141-144-73-180.vpn.oracle.com by acsmt350.oracle.com with ESMTP id 3018058241183746372; Fri, 06 Jul 2007 11:26:12 -0700 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Importance: Normal X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-kernel: Linux 2.4-2.6 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:16099 Archived-At: > > I added this text to the above entry: > > > > If you want the old behavior back, put these two key > > bindings to your ~/.emacs init file: > > > > (define-key minibuffer-local-filename-completion-map > > " " 'minibuffer-complete-word) > > (define-key minibuffer-local-must-match-filename-map > > " " 'minibuffer-complete-word) > > > > Does it give you enough information now? Did the recipe work for you? > > Many thanks. It does work as suggested with the above code snippet. > As for the documentation, well yes that would make sense. But would > it be also useful to put it under Emacs-Minibuffer-Completion Commands > section in the info manual? > > Similar to the way, how Emacs recognises sentences (2 spaces vs > 1aftera period) and how the manual explains how to switch from one to > the other, I think, there should be a similar explanation in the main > info manual. Rather than pepper the manual with this kind of thing, I'd rather see all such ways to obtain previous-release behavior documented in a single place.