Re: Entering filenames with spaces

[David Kastrup]

Thien-Thi Nguyen <address@hidden> writes:

> David Reitter <address@hidden> writes:
>
>> I respectfully agree for the UI reasons I mentioned before. Why not
>> map 'x' to the completion function? After all, only a few file names
>> have an 'x' in them!
>
> traditionally, spaces in filenames break lots of unixoid tools,

Wrong.  Spaces in filenames are no problem to pretty much _any_
"unixoid" tool.  The only place where they need escaping is in shells;
and if you use file name completion, it will be provided automatically
(i.e. by bash).

Since desktop environments become more and more common for unixoid
systems including free systems, spaces in file names become more and
more common as well: certainly more common than most other special
characters in file names.

> and were thus generally shunned (finicky quoters excepted).  thus,
> any argument based on favoring the many at the expense of the few
> will work both for and against keeping the default binding,

The "many" are not just Windows users (by the way: spaces need quoting
in the Windows command line, too).  They are all users that don't rely
on the command line for most of their work.  And that certainly
includes most users of free systems.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum