James G. Sack (jim) wrote:
I was going to say that Windows actually has a more sensible policy on
filenames, but maybe that is just pre-ntfs
http://en.wikipedia.org/wiki/Filename#Comparison_of_file_name_limitations
Regards,
..jim (why don't we just use inodes?)
The issue really isn't the filesystem. It's the shell.
All of our shells use whitespace as a delimiter; consequently, we need
to use quoting to get at whitespace when we need it somewhere else.
The big issue for me is not the quoting, I can deal with that. The real
question is *who handles the quoting*. Since command line arguments get
expanded before being handed to the application, the application can
never tell what you meant.
This is a result of not having a C library that handles
quoting/expansion/glob of args. Thus, who expands which characters is
always a nice thicket of mud.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
