> A rather unusual but completely legal file name. Its quite legal to have both
> bash\r and bash as two totally different interpreters.
In this manner, it is also possible to construct names with \n. So how are you
to correctly find bash\n with the current parsing?
> Next people will want the kernel to automatically decode scripts accidentally
> saved in ms word format.
This is a slippery slope argument. If there were a large enough user base of
people accidentally saving files in ms word format, and it was a one line fix,
and it didn't break anything else, then I would agree with you that the kernel
should support this.
But you probably have better things to do than argue with the likes of me.
Thanks for the joust.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/