Re: modern Applicard

["Jeff Blakeney" <jeff.blakeney@a2central.com.remove-vb9-this>]

  To: a2retro
On Sat, 6 Dec 2008 23:41:32 -0500, a2retro wrote:

> Steven Hirsch wrote:
>> Jeff Blakeney wrote:
>> 
>>> Are spaces illegal characters in filenames under UNIX?  If so, how do
>>> you get a file with spaces stored on your machine in the first place.
>> 
>> No, not illegal.  Just a PITA, since you need to put them in quotes when 
>> passing them on the command line.

Well, I guess we have different ideas about what is a PITA.  :-)  I
don't see putting quotes around parameters as much of a problem.  I do
it with the Windows command line all the time.

I often will skip spaces in filenames myself but I avoid using
underscore because it isn't the easiest character to type and I
personally think it looks ugly.  I will sometimes use periods instead of
space but usually just skip spaces all together and use capitalization
to separate words.  Mind you, this could also be considered a "PITA" for
UNIX users seeing as that operating system's filenames are case
sensitive.  :-)

> This discussion kinda reminds me of the "toilet seat up or down" 
> discussion my wife and I have every so often  ;-)
> 
> What's good for you might not be good for me :)

Too true.  I tend to not complain about these sorts of things because,
if I don't like the filename of a file I download, I just change it to
whatever name I prefer.  I do this all the time because I find most
files either have ugly names or names that don't describe their contents
much, if at all.  :-)