why settle for \n when you can go for the stylish carriage return

It's time to log off and get a vasectomy

This sounds like the start of another sovcit "loophole"

A line break is a non-printable character. So it would only work in the scope of electronic storage. The minute it hits other media, the line break character is subject to how that media handles it’s presence, and then it is lost permanently from that step forward.

Plus, many input forms make use of validation that will just trim anything that isn’t a character or number, removing the line break character.

What about an open bracket? (

Always sanitize your Data inputs.

Anyone remember when Chrome had that issue with validating nested URL-encoded characters? Anyone for John%%80%80 Doe?

Am I allowed to include sql command words such as drop table in my child's name?

I'm not american and I'm glad I'm not but intended if someone could enter a bunch of zero width spaces

Unix or dos format?

Anyway, you probably need to put a backslash before it to indicate line continuation.

But wouldn't it be better to use something more traditional, such as ?