unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Entering filenames with spaces
Date: Mon, 07 Nov 2005 10:34:31 -0500	[thread overview]
Message-ID: <E1EZ90x-00057K-7Y@fencepost.gnu.org> (raw)
In-Reply-To: <CCA0AF84-439B-4906-8052-B7B607BBB0F6@gmail.com> (message from David Reitter on Sat, 5 Nov 2005 15:02:30 +0000)

It is pleasingly simple.  I have a few comments on details.

    +   initial_define_key (Vminibuffer_local_filename_completion_map, '\t',
    + 		      "minibuffer-complete");
    +   initial_define_key (Vminibuffer_local_filename_completion_map, '?',
			  "minibuffer-completion-help");

I think it would be cleaner to use Vminibuffer_local_completion_map
as this map's parent, and override only the SPC character.

    *** For filenames, Space is not bound to completion any longer

You need a period after that.  Also, it should be "SPC", not "Space".

    Filenames with spaces can be input intuitively with the space bar now,
    space is not bound to `minibuffer-complete-word' any longer.

That should be "SPC", not "space".  Also, it is a run-on sentence.

    A new key map minibuffer-local-filename-completion-map applies whenever
    a file name is prompted for.

That is passive--please rewrite it in the active voice.

  parent reply	other threads:[~2005-11-07 15:34 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 11:22 Entering filenames with spaces David Reitter
2005-08-12  7:51 ` James Cloos
2005-08-12  9:37   ` Lennart Borgman
2005-08-12 10:26     ` James Cloos
2005-08-12 13:13       ` David Reitter
2005-08-12 15:15   ` Drew Adams
2005-08-12 15:40     ` Andreas Schwab
2005-08-12 15:58       ` Drew Adams
2005-08-12 16:26         ` David Reitter
2005-08-12 17:50           ` Drew Adams
2005-08-12 19:28             ` David Reitter
2005-08-12 21:47               ` Drew Adams
2005-08-13  0:55               ` Thien-Thi Nguyen
2005-08-13  8:27                 ` David Kastrup
2005-08-13 16:48                   ` Thien-Thi Nguyen
2005-08-13 17:51                     ` David Kastrup
2005-08-13 21:14                       ` Thien-Thi Nguyen
2005-08-13 12:11           ` James Cloos
2005-08-12 19:23     ` Lennart Borgman
2005-08-12 19:51       ` Drew Adams
2005-08-12 20:22         ` Lennart Borgman
2005-08-13  6:11         ` Juri Linkov
2005-08-13 14:40     ` Richard M. Stallman
2005-08-14  3:48       ` Eli Zaretskii
2005-08-14  6:20         ` Stefan Monnier
2005-08-14 19:06           ` Eli Zaretskii
2005-08-15  7:58             ` Kim F. Storm
2005-08-15 19:35               ` Eli Zaretskii
2005-08-14 21:03         ` Richard M. Stallman
2005-10-15 17:42       ` David Reitter
2005-10-17  4:33         ` Richard M. Stallman
2005-10-18  9:26           ` David Reitter
2005-10-18 15:06             ` Drew Adams
2005-10-18 15:39             ` Stefan Monnier
2005-10-19  2:43             ` Richard M. Stallman
2005-11-05 15:02               ` David Reitter
2005-11-05 16:34                 ` Drew Adams
2005-11-06 16:15                   ` David Reitter
2005-11-06 17:36                   ` Richard M. Stallman
2005-11-07  1:48                     ` Drew Adams
2005-11-07 14:34                   ` Juri Linkov
2005-11-07 21:56                     ` Richard M. Stallman
2005-11-07 15:34                 ` Richard M. Stallman [this message]
2005-11-14 11:18                   ` David Reitter
2005-11-14 13:27                     ` Stefan Monnier

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=E1EZ90x-00057K-7Y@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@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).