On Mon, 27 Mar 2006, Jon LaBadie wrote:
> On Mon, Mar 27, 2006 at 08:12:00AM -0600, Graeme Humphries wrote:
> > stan wrote:
> > > Right, spaces in filenames is a disease.
> > Why?
> > > The vector for spreading this disease has largely been microsloth, and 
> > > all of the uneducated users they
> > > brought to the party.
> > >   
> > Why does spaces in names = a lack of education? Perhaps the clearest way
> > to label a file includes a space?
> > > Not a reason _not_ to handle them corectly, though, just an editorial
> > > comment.
> > >   
> > IMO there's nothing intrinsically wrong with any character in a file
> > name, as long as it makes sense with regards to your naming conventions.
> > The only difficulty it causes is if your tools can't handle that
> > character very well. These days, *even* on UNIX, most tools should
> > handle spaces in filenames just fine.
> 
> GUI tools perhaps.  I think command line tools will always have
> the difficulty of "what character or sequence is the separator
> between arguments".

That's what single and double quotes, and backslashes are used for...

Gr{oetje,eeting}s,

                                                Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert AT linux-m68k 
DOT org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                                            -- Linus Torvalds