-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: Use RGA for VSCode Search #257
Comments
I think you can choose the path to rga somewhere in VSCode settings? just setting that to rga might work |
Agreed with phiresky's suggestion. |
Thanks for the info, good to know that the CLI is compatible. The |
There isn't a setting for this but as I my last comment shows, you can just go replace the executables which has the same effect. |
rga might require rg and rga-preproc to be next to the rga binary make sure those are there |
Good point. Looks like it doesn't make a difference though. I tried renaming them to |
yeah, could be that vscode calls rga but then rga calls the "rg" binary which is just rga again so it's an endless loop |
I believe VS Code uses ripgrep under the hood to search across all files in the opened directory(s) (https://github.com/microsoft/vscode-ripgrep?tab=readme-ov-file).
I'd be curious how feasible it would be to drop in ripgrep-all instead of ripgrep so that VS Code provides richer search results for PDF etc. I know this breaks down at some point, e.g. in VS Code you click on a result to jump to the line number where the match is found, and that might not be possible for many files with rga. Still, I think about this daily and even just opening the file itself is rga detects a match would be very helpful.
I'm not very familiar with the input argument syntax for rg vs rga, so I'm not sure if this would be very easy or very hard to accomplish - curious to hear feedback.
The text was updated successfully, but these errors were encountered: