[dundee] BashPitfalls

[Martin Habets]

On Wed, Feb 09, 2011 at 10:37:50PM +0100, Axel wrote:
> In circumstance you have to port your program to another
> operation system such as Windows, you have to avoid this or is will
> be crashing. There are directories like "Documents and Settings",
> which contain spaces.

I must say, that one still puzzles me. Took me quite a while to figure out
how to cd into that directory. Tried "cd Document~1" and stuff like that
for a while. Frustrating...

Nowadays I usually avoid it, sftp my work between C:\TEMP and the Linux
machine.
Would windows allow me to rename that directory to Documents_and_Settings,
or will it insist on the spaces?

Martin

> I take the view, both ways are bad. Spaces in file names make
> working with the command line
> much complicated and programs which ignore spaces are not reliable
> in their behaviour.
> 
> Quoting James Le Cuirot <chewi at aura-online.co.uk>:
> 
> >On Wed, 9 Feb 2011 16:25:54 +0000
> >Andrew Clayton <andrew at digital-domain.net> wrote:
> >
> >>> These are some very negative attitudes. I sometimes use spaces for
> >>> stuff in my home folder. I certainly use them for my music files.
> >>> I
> >>
> >>Why? Assuming your music is properly tagged (why wouldn't it be?) then
> >>spaces serve no purpose.
> >
> >My music is tagged properly and I must admit, I don't have a good a
> >answer for that, but I feel my point still stands. Good coders should
> >always take them into account.
> >
> >James