There is already guidance on the tag text-processing
in the tag wiki, which I think covers the issue quite well.
Unix systems tend to favor text files, often consisting of one record
per line. Most Unix configuration files are text files. Unix systems
come with many tools to manipulate such files. Most tools process the
file in a stream: read a line, process it, emit the corresponding
output; this makes it possible to chain scripts with pipes.
Use this tag when your question is about processing text files and
you're not sure which tool to use. If your question is about a
specific tool, use its tag.
I believe when this topic has come up in the past we've rationalized it like this.
- Try to get clarification from the OP if they strictly want an
sed, etc. solution or are open to any command. Both situations come up.
- We're generally very tolerant on unix.stackexchange.com vs. other SE's with respect to not flagging answers to questions that make use of alternative tools, when a question is tagged with something specific.
- Part of our interaction with OP's is to help get this clarification up front via comments, before providing a solution, so we should focus on doing this as the questions come. Often times, users new to Unix are unaware that they have choices. They will have some vague notions about there being tools like
sed, etc. but don't fully grasp their subtleties.
Cleaning up the site is always an appreciated service so I would encourage you to pull some searches together to get an idea of how many questions we're looking at here and then post another question on meta to help track the work. Let us know through comments/chat if you're unclear how to proceed and what tasks you need others to help with.
We'll generally post a search or list of questions and divide the work up amongst other members so that it isn't too burdensome for a single individual.