the_silver_searcher VS sd

View on GitHub

If you have trouble finding it among the other stuff happening in the server log, well, so do I! I recommend learning how to programmatically search through your terminal output. Providing a universal method for this is challenging because various tools and terminal emulators implement this functionality differently. Another option would be to use tools like grep or the_silver_searcher (a favorite of mine) to search the file where your dev logs are written to. This file is located at log/development.log in a Rails project.

Some of the examples below use ag, but could just as well use grep or equivalent.

Why guess when [there are installation instructions for various platforms on the README](https://github.com/ggreer/the_silver_searcher#installing)?

Also, although it may not be easy to remember, is this really a problem in practice given the installation count in most contexts is one? If there's a context where it's installed regularly, that's a one-time addition to an install script, Dockerfile, etc. in my experience. Do you have a situation that isn't amenable to that?

The kernel changes a lot, so the books would get outdated quickly. But you can find simple / similar drivers, and read the code. Usually there are some documentation / comments on the headers before the function declarations. The Elixir and the Silver Searcher will help a lot.

URL 🔗 : https://github.com/ggreer/the_silver_searcher

My "vim" way of finding all the places where a function is being used: using visual mode, marking the function, and passing it to :Ag (silversearcher) The problem with this is that it is not 100% accurate, since it will just look for things with the same name, so I was thinking about using the LSP to make things more robust.

We're fans of ag, The Silver Searcher.

Helm-ag is an interface to the ag, silver-searcher, so check the docs for ag. For example, ag automatically ignore some files if there is a .gitignore with some file patterns, or you could use .agignore.

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.