Linux Systems

Unix is very permissive with filenames, and this can sometimes lead to a bunch of annoying corner cases when printing files. A well known example is when you put a newline in a filename, and it breaks naive parsing of a file list later in the pipeline.

There's not much mystery around why Unix decided to be permissive with filenames, so I'm not asking why newlines are allowed in filenames.

However, are there any situations where it is useful (or necessary, or desirable...) to have newlines in filenames? Hypothetical is okay, but "in the wild" would be even better.

I've only seen it when someone is deliberately trying to set up a trap (hacking, pranks) or by accident (programmer forgot to add a whitespace normalizer to their filename generator).

is a duplicate

This question has been asked before and has already been answered. It should be marked as a duplicate.

Please enter the URL of the proposed duplicate in the details field below.

not constructive

This question cannot be answered in a way that is helpful to anyone. It's not possible to learn something from possible answers, except for the solution for the specific problem of the asker.

Communities

Comments on Are there any legitimate uses for newlines in filenames?

Are there any legitimate uses for newlines in filenames?

3 comment threads