Re: minibuffer-complete-word
-- Jeff Mincy <jeff(a)delphioutpost.com> spake thusly:
minibuffer-complete-word is has a feature that I find annoying.
If you have the following files:
~/foo.zzy
~/foo-bar
~/foo bar
Then minibuffer-complete-word completes 'foo' then completes "foo
bar", with no indication that there were other files to complete.
Perhaps minibuffer-complete (which is bound to tab rather than space)
is more what you're looking for. For instance, with the aforementioned
files, I do:
C-x f ~/f [space] [space] [space]
and XEmacs find "foo bar", as you said. This actually makes sense in
the context of the files that are there. When the second space is
typed, it matches the space in "foo bar" and therefore is inserted.
Then when the third space is typed after "foo ", the only thing left to
match is "foo bar".
However, if I do:
C-x f ~/f [TAB] [TAB]
XEmacs simply lists the possible completions. If you really don't like
minibuffer-complete-word at all, you could bind minibuffer-complete to
space and probably never worry about it again.
Attachments:
- attachment.sig (application/pgp-signature — 232 bytes)