On mié, 2007-12-19 at 16:08 +0100, Herman Robak wrote: > On Wed, 19 Dec 2007 15:40:05 +0100, Burkhard Plaum > <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > Herman Robak schrieb: > >> On Wed, 19 Dec 2007 09:15:02 +0100, Kerneels Gouws <[EMAIL PROTECTED]> > > > >> 1) It is something you are doing. If you're on Linux or some other > >> UNIX, > >> you DON'T want to have spaces in directory or file names. It breaks > >> things! > > > > Disagree. > > Spaces are perfeclty legal in UNIX filenames. > > Yep. Some non-printable characters are legal, too, if I am not mistaken. > Non-printable characters in file names can trick the user. White-spaces > in file names can cause "interesting" things in shell scripts.
I don't know what POSIX requires, but most modern file-systems that Linux supports allow any byte sequence as long as it doesn't contain the directory separator (i.e. the slash). > Not all legal filenames are wise file names. That's no reason why a piece of software should place additional constrains. > > UNIX Software, which doesn't support all legal UNIX filenames, is broken. > > Most shells are broken in that sense. And that's quite annoying. Broken in what way? It would be nice to get them fixed where possible. I mostly use bash and save for my own mistakes, I've never had problem escaping file names. Besides, an application shouldn't rely in the shell parsing the command-line, it should pass each argument in a string, as someone else already pointed out in this thread. Greetings, -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
