ctpv VS sd

And proper previews can be provided by https://github.com/NikitaIvanovV/ctpv

Link: https://github.com/NikitaIvanovV/ctpv

You can find an example here. It's a bit more complex but generally it's the same. The rule for compiling object files is not there though because in GNUmake it's a predefined rule but I added it in the tutorial above for completeness.

Btw, this is the code for lexer if you want to take a look: https://github.com/NikitaIvanovV/ctpv/blob/master/src/lexer.c

View on GitHub

I wanted to like sd but it doesn't support my main use case of recursive search/replace. Imagine every time you wanted to grep some files you had to build a find+xargs+rg pipeline... it just takes me out of the flow too much. I'm glad people are posting other options here, I'm looking forward to trying them.

https://github.com/chmln/sd/issues/62

sd

https://github.com/chmln/sd ftw (sed rebuilt in rust, much easier imho) ;-)

sd is a more intuitive alternative to sed, focussing on making find and replace easier - which is all I ever used sed for.

https://github.com/chmln/sd

If it's in multiple files? To be honest, I'd just use a terminal and sed (or sd if you want something with a more friendly interface).

I love the idea and I'll try it out, but a heads up in case the author is around: the name sd clashes with another tool [0], which works as an alternative to sed.

I use that one pretty often, so maybe my first managed script will be one which symlinks binaries :)

[0] https://github.com/chmln/sd

sd is a find-and-replace CLI, and you can use it as a replacement for sed and awk. It is way more user-friendly and modern. It is also magnitudes faster than sed.