As it stands, it seems that one cannot save a buffer to a new file
with a name that contains space characters, at least not in a
straightforward way.
The reason is that the minibuffer that prompts for input does not
accept space as an input character for the string that is read - even
On 25 Jun 2005, at 14:16, David Reitter wrote:
As it stands, it seems that one cannot save a buffer to a new file
with a name that contains space characters, at least not in a
straightforward way.
The reason is that the minibuffer that prompts for input does not
accept space as an input
On 6/26/05, David Reitter [EMAIL PROTECTED] wrote:
How is a user supposed to know about C-q? Checking the manual for
something as simple as entering a file name is ridiculous, and even
if you do a C-h k C-x C-f (which is probably the obvious place for a
new user to look).
C-q has nothing to
On 26 Jun 2005, at 01:24, Miles Bader wrote:
How is a user supposed to know about C-q? Checking the manual for
something as simple as entering a file name is ridiculous, and even
if you do a C-h k C-x C-f (which is probably the obvious place for a
new user to look).
C-q has nothing to do
minibuffer-local-completion-map binds the space character to
minibuffer-complete-word (defined in src/keymap.c).
If the users would be happier if we turned off word-completion in
reading file names, I would not object. I don't believe I ever use
this feature for file names. Does
