51–60 of 73 posts
rg is great, I use it a lot. Recently I have also used [ambr]( https://github.com/dalance/amber ) which can do both search (ambs) and replace (ambr) recursively in your codebase. The only problem as of yet is that it does not support globbing so I cannot filter on certain filetypes only.
so... its grep to ack to ag to rg, is there something next?
Earlier quoted context omitted.
I wanted to like sd but it doesn't support my main use case of recursive search/replace. Imagine if every time you wanted to grep some files you had to build a find -print0 | 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
If you haven't discovered recursive path expansion with `**` yet, which is supported by a number of popular shells, including bash, it is about to improve your shell life.
Also, for a "confirm your changes" type workflow, I like git add -p after running the sd command just to review all of the changes.
There is a distinct joy in showing someone rg who has never seen it before and then seeing them immediately adopt it as a daily tool. Recently a colleague had a bug. He told me it was related to the "X" that was weirdly behaving like a "Y". I fd'd "X" and then rg'd the resulting files for "Y" and found a place where some copy/pasted code was treating "X" as a "Y". Big monorepo codebase, absolutely just tore through i…
Earlier quoted context omitted.
I wanted to like sd but it doesn't support my main use case of recursive search/replace. Imagine if every time you wanted to grep some files you had to build a find -print0 | 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
If you haven't discovered recursive path expansion with `**` yet, which is supported by a number of popular shells, including bash, it is about to improve your shell life.
There is a distinct joy in showing someone rg who has never seen it before and then seeing them immediately adopt it as a daily tool. Recently a colleague had a bug. He told me it was related to the "X" that was weirdly behaving like a "Y". I fd'd "X" and then rg'd the resulting files for "Y" and found a place where some copy/pasted code was treating "X" as a "Y". Big monorepo codebase, absolutely just tore through i…
There is a distinct joy in showing someone rg who has never seen it before and then seeing them immediately adopt it as a daily tool. Recently a colleague had a bug. He told me it was related to the "X" that was weirdly behaving like a "Y". I fd'd "X" and then rg'd the resulting files for "Y" and found a place where some copy/pasted code was treating "X" as a "Y". Big monorepo codebase, absolutely just tore through i…
Since Visual Studio Code is using ripgrep for search one can also open the repo in the editor and use find in files to search for such things similar performance. It’s one of my favorite tools for searching specific expressions in codebases.
I don't think it's ripgrep itself, it's something with the way VSCode manages extensions, and doesn't give you enough information to debug which extension is blocking it.
so... its grep to ack to ag to rg, is there something next?