ack3 VS the_silver_searcher

fyi ack is like this but for perl instead of python https://beyondgrep.com/

If you just need a single shell command you can do :!. Example:

:!ack "stupid_structure->who_wrote_this_crap.oooohhhhh\s+="

(and if you wonder what "ack" means: https://beyondgrep.com/)

Ack is consistent with grep but will sensibly handle the recursive stuff for you.

Scan the file tree containing the website for the links, or part of tje links, for example with ack which is an easy to use, recursive reimplementation of grep.

I've thought about redoing ack in Python but it wasn't any faster than the current Perl.

Ever hear of ack it might be a faster alternative.

No, but thanks for pointing out its existence. Homepage:

https://beyondgrep.com/

(ack comes from ack-grep, a better version of grep, but you can just replace it with grep -r)

I've been a fan of ack for quite some time.  Somehow (and I'm not quite sure how) once or twice it's found stuff in source code that VSCode simply misses (likely I was searching wrong with VSCode).  And there are a few things I've found that make it even more effective in searching Elixir code that I thought I'd share.

Very much agreed. I'm a developer and I honestly prefer ack (https://beyondgrep.com/) myself. But it has the exact same issue. It's not standard.

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.