On 9/9/07, John Cowan <[EMAIL PROTECTED]> wrote: > > Lasse Kliemann scripsit: > > > Yes. Most Unix filesystems allow filenames that contain newlines. Hence > I > > have to expect them when I process files that have not been created > directly > > by me (but by a user, by unpacking a tar file from an external source, > by > > some (stupid) software, ...). > > Well, I can't stop you from worrying about it, but delicately I suggest > that such concern is excessive. > > -- > Why are well-meaning Westerners so concerned that John Cowan > the opening of a Colonel Sanders in Beijing means [EMAIL PROTECTED] > the end of Chinese culture? [...] We have had > http://www.ccil.org/~cowan > Chinese restaurants in America for over a century, > and it hasn't made us Chinese. On the contrary, > we obliged the Chinese to invent chop suey. --Marshall Sahlins > > > _______________________________________________ > Bug-coreutils mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/bug-coreutils >
(This is slightly off topic, and a late reply) I'm curious who's responsible for deciding the standards of filenames. Is it kernel people, fs people, a standards group, or other? And are there benefits of allowing control characters in filenames? Steve Ward _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
