You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been a user of ripgrep for a while but just discovered ripgrep-all while looking for the solution to a specific issue, but it's great to have such a general tool.
The problem is to search through an entire Unison codebase, which are stored in sqlite files. A quick test with rga indicates I can find stuff I'm looking for, but not much helpful context (e.g. the namespace that the code is coming from):
As a Unison user, ideally I'd be able to just use the existing functionality to search through a unison sqlite file or any other sqlite file, and allow the existing adapter to recognize if a sqlite file is unison by inspecting database metadata. That said, it is hard to imagine a time at which a significant portion of ripgrep-all users are also Unison users (fwiw, I love Rust and Unison!). So maybe having a config option to disable the Unison check by default would be an option, though checking metadata should be relatively quick I imagine.
The other option is to just have a separate adapter, which is certainly ok in principle, I think, but I wonder if it might conflict with the existing adapter when looking at file extensions and creating metadata; since there is overlap, it seems like we may need the same metadata generation code to determine which adapter to use: sqlite or unison-specific sqlite.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I've been a user of ripgrep for a while but just discovered ripgrep-all while looking for the solution to a specific issue, but it's great to have such a general tool.
The problem is to search through an entire Unison codebase, which are stored in sqlite files. A quick test with
rga
indicates I can find stuff I'm looking for, but not much helpful context (e.g. the namespace that the code is coming from):As a Unison user, ideally I'd be able to just use the existing functionality to search through a unison sqlite file or any other sqlite file, and allow the existing adapter to recognize if a sqlite file is unison by inspecting database metadata. That said, it is hard to imagine a time at which a significant portion of ripgrep-all users are also Unison users (fwiw, I love Rust and Unison!). So maybe having a config option to disable the Unison check by default would be an option, though checking metadata should be relatively quick I imagine.
The other option is to just have a separate adapter, which is certainly ok in principle, I think, but I wonder if it might conflict with the existing adapter when looking at file extensions and creating metadata; since there is overlap, it seems like we may need the same metadata generation code to determine which adapter to use: sqlite or unison-specific sqlite.
Beta Was this translation helpful? Give feedback.
All reactions