spaces in filenames

[David C. Ullrich]

Neil Schemenauer <nascheme at enme.ucalgary.ca> wrote in article
<slrn8k2o30.3r4.nascheme at cranky.arctrix.com>...
> Tim Peters <tim_one at email.msn.com> wrote:
> >I strongly recommend one deviation from the defaults, though:
> >when it asks for the Python installation directory, force it to
> >"c:\python15" (where "c:\" is the root of his boot drive, almost
> >certainly exactly "c:\"). The default is some monster with
> >embedded spaces in its name, and that just makes life harder.
> 
> This is something that pissed me off about Windows 95.  Microsoft
> just had to show off their new feature allowing spaces in
> filenames by putting a space in one of the most important
> directory names on the system.  Unix has allowed weird characters
> in filenames for ages.  Just because you can do it doesn't mean
> its a good idea.  I wonder how much time has been wasted
> worldwide because Microsoft did not call "Program Files"
> "Programs".

          My opinion is they did it on purpose. A program is required to
be able to handle funny filenames to qualify as Windows 95 
compatible blah blah, so this is like a test.

          Pisses me off too. Long filenames great, but allowing
spaces is just silly, when spaces have been command-line
delimiters all along. (Wasted a lot of time once finding out
why a certain TeX file didn't work - turns out there's a reason
MikTeX doesn't install itself under Program Files...)

>     Neil
> 
> -- 
> "Reliability means never having to say you're sorry." -- D. J. Bernstein
>