Hello! I'm the author. This is similar in vein to useful-sed, a surprisingly successful github repo (which can be found here https://github.com/adrianscheff/useful-sed).
If you have any questions, suggestions or simply feedback - let me know.
Hey there! Thank you for the input!
I'm sorry you feel that asking for donations is unwarranted. I agree wholeheartedly that FSF deserves all the love it can get. I'm not asking to get rich or take the spotlight - I'm asking so I can keep improving that guide & create more.
I didn't added explanations (although I wanted too) since this was intended as a quick tips page for sed. I think there are much better guides than I could ever make (including the info page). In a way it works better since it's more digestible.
Thank you for the link you provided - it looks awesome! I'll look into it and append the existing guide if needed (while giving credits of course)
Thank you for the constructive feedback, I've corrected the mistakes pointed out. I've also changed -r to -E based on your (and some other people's) advice.
Thank you for your feedback! Personally I very rarely use the ; operator since it works badly with braces and commands that use files.
However I've added an example using the ; operator.
PS: May I humbly point out that the command you provided will actually print up to line 10 and then a duplicate line. Like I said, unexpected (even though it seems logical). :)
I'm glad to hear that. I'm learning (and re-learning) sed myself, specially after long periods of not using it. So in a way I've written it for me too.
Btw, there is one more use case of a variable delimiter which is more arcane (and you can combine it with the other custom delimiter)
`sed -s '\_/bin/bash_s:grep:egrep:' myfile.txt`
Thank you for the feedback and the constructive criticism.
Regarding the hold space I found it very confusing to use and understand. IMO it represents the 80/20 of sed (80% effort for 20% results).
You're right, I'm using -r even when it's not necessary. To my defense I think it's a good habit to have since without it regex expressions are painful to write.
I didn't considered that using -E it's a better choice but I'll correct that now. (one might argue again that typing -r is easier than -E :D ).
Regarding the definition of words - I also thought of that when I wrote that snippet. I know it's not the complete regex for a word and that word regex patterns might differ. And I was probably a bit lazy - but I'll correct it presently.
I'd also like to say that I didn't write this as an absolute and ultimate reference. If I'm honest I wrote this as much to teach others as to solidify this knowledge myself.
Now since it seems it gained traction I'm kinda obligated to make this better, no? Darn. :)
PS: if you'd like to help me make this better please submit a pull request or leave a comment here. Looking at your profile I see that you try to limit your online time so I probably shouldn've asked. :P
For those curios, the backend is Go+Echo+Templ, frontend is Materialize+jQuery.