On Tue, 10 Nov 2009 09:50:33 -0800, Darren New wrote:

> clipka wrote:
>> On unix, where even now it is still quite common to do stuff in some
>> command line shell, it is pretty uncommon to put blanks in filenames,
>> because it would be a hassle to even "cd" there.
> 
> That used to be true back in the 1.x days of Linux (like, 10 years ago),
> but nowadays I haven't had much problem with spaces in file names,
> except in lazy scripts I've written myself using "$@" and such. (And
> that's more because it's easier for me to skip the one-line script than
> to look up the proper quoting mechanism to get that in.)
> 
> Bash command-line completion, for example, will put quotes around names
> with spaces in them.  But yes, this wasn't always common, even long
> after Mac and Windows commonly used spaces in names.

Even still, though, on Linux you can run into problems with spaces in 
names.  Using scp to copy files from one openSUSE 11.1 box to another, 
for example, spaces (escaped and quoted) always cause me a problem.

Jim

Post a reply to this message