- I can’t control what someone else checks into their repo. I use web frontends for code search almost exclusively on other people’s repos, because my own repos are already on my machine, so what’s the point.
- Most of the time I don’t want to see search results in tests, but occasionally I actually want to find things in tests and not anywhere else. Different people have different filtering needs at different times, you can’t have a ignore file that satisfies every need. Search is about filtering to begin with.
Well, all this tool does is calling rg from a directory with a bunch of repos, so providing global filters on every query is as awful as rg providing a --glob flag... Which is arguably not that awful to a lot of users.
> Datasette is a tool you run against your stuff usually. ... datasette runs locally.
I don't think so? I could be wrong but I thought a major use case (or the major use case) is providing a frontend for your data to other people. Like on https://ripgrep.datasette.io/-/ripgrep.
> Datasette is aimed at data journalists, museum curators, archivists, local governments and anyone else who has data that they wish to share with the world.
> I don't think so? I could be wrong but I thought a major use case (or the major use case) is providing a frontend for your data to other people.
_I_ use datasette and I only ever used it locally or in a docker container. In either case for datasette-ripgrep to work you need to check out the repos you want to search in one folder that datasette will then invoke ripgrep on.
There are folks that publish datasette installations for public consumptions but even in that case I would assume that code search was preconfigured to make any sense with ignore files.
>> Datasette is aimed at data journalists, museum curators, archivists, local governments and anyone else who has data that they wish to share with the world.
That doesn't preclude installing the program locally.
The official "getting started" talks of remote / web datasettes as "demos" and "trials".
> That doesn't preclude installing the program locally.
Of course not. But the project makes it pretty clear that it's designed with multiuser in mind. Can you host multiuser web apps only for yourself? Of course, I do that all the time. The unreasonable thing is saying "I use this thing exclusively for my own stuff on my local network, so screw your requests for multiuser, public-facing use cases."
- Most of the time I don’t want to see search results in tests, but occasionally I actually want to find things in tests and not anywhere else. Different people have different filtering needs at different times, you can’t have a ignore file that satisfies every need. Search is about filtering to begin with.