Submission + - Are spaces in filenames worth it?
innocent_white_lamb writes: After yet another episode of having a perfectly good script (this one straight out of a book, in fact) fail due to a space in a filename, I was just thinking.... Do you think that the "convenience" of having spaces as allowed characters in a filename outweighs the special processing that having a space in a filename requires when you are trying to do something from the commandline? Even if you're typing a simple command, you still have to use a \ in front of every space in the filename, which adds characters to what you're typing. And in bash scripting you get into little joys like single and double quotes and so on.
In the day of DOS, you had to work at it to get a space into a filename. (And with 8.3 you generally wouldn't want to waste that character even if you could do it easily.)
My Letter to Aunt Sally.txt is indeed somewhat more readable than MyLetterToAuntSally.txt, but is it sufficiently better as to justify the additional special handling it will require if you're trying to deal with it from a commandline?
In the day of DOS, you had to work at it to get a space into a filename. (And with 8.3 you generally wouldn't want to waste that character even if you could do it easily.)
My Letter to Aunt Sally.txt is indeed somewhat more readable than MyLetterToAuntSally.txt, but is it sufficiently better as to justify the additional special handling it will require if you're trying to deal with it from a commandline?
