After working a lot with shell scripts, it turns out that one of the single most important concepts when handling arbitrary user input is the null character, aka. NUL, \0, ^@, and others. I added it to a question which included the line

Is there a way to detect NUL (\0) characters in sed?

but it was removed by a very high-rated user. Considering how important and difficult NUL handling is in for example Bash, shouldn't it be OK to add this tag (or null-separator/null-character) to such questions?


I don't see a problem with it. Possibly he removed it because questions can only have five tags, and he thought the tags he was adding were more important than that one


I removed the tag because it didn't seem to address the main points of the question, which were to detect files through commands, munge line endings () and do global file processing with — a task.

Furthermore, I'm not convinced of the usefulness of a specific tag for the null byte. Handling it is very closely related with handling data.

  • Yeah, I realized the bit about NUL bytes didn't really tie in well with the rest of the question, so I split it off. – l0b0 Apr 20 '12 at 7:26

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .