From: "Drew Adams" <drew.adams@oracle.com>
To: <bug-gnu-emacs@gnu.org>
Subject: RE: Insufficient documentation on *how* to change SPC behaviour inminibuffer
Date: Fri, 6 Jul 2007 11:26:07 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICMEODDNAA.drew.adams@oracle.com> (raw)
In-Reply-To: <uk5td8l63.fsf@gmail.com>
> > 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.
next prev parent reply other threads:[~2007-07-06 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 18:23 Insufficient documentation on *how* to change SPC behaviour in minibuffer Sivaram Neelakantan
2007-07-06 16:16 ` Eli Zaretskii
2007-07-06 18:03 ` Sivaram Neelakantan
2007-07-06 18:26 ` Drew Adams [this message]
2007-07-07 9:48 ` Insufficient documentation on *how* to change SPC behaviour inminibuffer Eli Zaretskii
2007-07-07 12:37 ` Insufficient documentation on *how* to change SPC behaviourinminibuffer Drew Adams
2007-07-07 20:47 ` Insufficient documentation on *how* to change SPC behaviour inminibuffer Richard Stallman
2007-07-07 9:46 ` Insufficient documentation on *how* to change SPC behaviour in minibuffer Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DNEMKBNJBGPAOPIJOOICMEODDNAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=bug-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).