On 10/24/07, Jeff Morriss <[EMAIL PROTECTED]> wrote: > Since it's primarily Windows that should have this problem (AFAICR most > *NIXs allow anything other than "/" in a file name) it should be easy > enough to find a list of prohibited chars.
in *NIX filenames with spaces are particularly tedious... I personally would forbid spaces in filenames en-toto as they tend to make scripts fail... [id-est:~/tt] lego% echo a b > a\ b [id-est:~/tt] lego% echo c d > c\ d [id-est:~/tt] lego% head * ==> a b <== a b ==> c d <== c d [id-est:~/tt] lego% find . -type f ./a b ./c d [id-est:~/tt] lego% grep a `find . -type f` grep: ./a: No such file or directory grep: b: No such file or directory grep: ./c: No such file or directory grep: d: No such file or directory -- This information is top security. When you have read it, destroy yourself. -- Marshall McLuhan _______________________________________________ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
