If you’ve been using Linux for any small length of time,
you’ve likely used sed before.
Most of the time, you’ve seen it in the form of sed "s/find/replace/g",
so you simply go to it whenever there’s a replacement you want to do.
But sed stands for stream editor,
and as a tool it can do more than just find and replace.
Feedback is still welcome, either here or as Merge Requests to my Gitlab Pages repo.
Never quite understand what sed is designed for. It seems to be able to do almost everything in the cost of complexity. Really useful when I need to hack together some config files for auto builds tho.
The name stream editor hints at its origin: It’s a strictly non-interactive implementation based on the standard Unix line editor ed – or technically qed, which is based on ed.
Never quite understand what
sedis designed for. It seems to be able to do almost everything in the cost of complexity. Really useful when I need to hack together some config files for auto builds tho.The name
streameditor hints at its origin: It’s a strictly non-interactive implementation based on the standard Unix line editored– or technicallyqed, which is based oned.