forkpkgs codesearch

janik commented

2024-08-01 13:23:04 +00:00

Owner

We want a code search as web interface for nixpkgs and potentially more projects, so developers can easily find code and reference it using a link.

A few months ago, source graph would have been basically the no-brainer solution, but they switched to a closed source license.

We have a few options here:

@jade suggested we could ask source graph to sponsor us a license. I personally would prefer to go with a FOSS solution to reduce our reliance on third parties.

TODO:

Decide on a codesarch solution
package/deploy it
integrate it with forkpkgs

We want a code search as web interface for nixpkgs and potentially more projects, so developers can easily find code and reference it using a link. A few months ago, source graph would have been basically the no-brainer solution, but they switched to a closed source license. We have a few options here: - https://github.com/livegrep/livegrep - https://oracle.github.io/opengrok/ - https://searchfox.org/ @jade suggested we could ask source graph to sponsor us a license. I personally would prefer to go with a FOSS solution to reduce our reliance on third parties. TODO: - [ ] Decide on a codesarch solution - [ ] package/deploy it - [ ] integrate it with forkpkgs

jade commented

2024-08-01 15:32:46 +00:00

Owner

i think most likely the only viable option of that list is searchfox. the others do not have precise code intelligence support which should be a non starter. ctags on web is just so silly.

i think most likely the only viable option of that list is searchfox. the others do not have precise code intelligence support which should be a non starter. ctags on web is just *so* silly.

raito commented

2024-08-06 19:21:20 +00:00

Owner

@jade could you expand on the precise code intelligence support that searchfox has? I was not able to find any information on that on searchfox (but it is likely that I missed it)

jade commented

2024-08-07 10:03:29 +00:00

Owner

You may observe that it has very consistently correct c++ navigation. this is due to the clang plugin they use. I've not done much more research other than seeing there's a clang plugin, though.

tom-hubrecht commented

2024-08-09 14:42:51 +00:00

Owner

From what I can see it will not work on nix files, unless a specific plugin is written

This step processes C++, Rust, JavaScript, and IDL files.

From what I can see it will not work on nix files, unless a specific plugin is written > This step processes C++, Rust, JavaScript, and IDL files.

raito commented

2024-08-09 14:48:28 +00:00

Owner

In the ideal world, a tool should use https://lsif.dev/ so we can provide a Nix LSIF.

raito commented

2024-08-09 14:49:16 +00:00

Owner

(or https://sourcegraph.com/blog/announcing-scip but unsure.)

jade commented

2024-08-09 19:27:57 +00:00

Owner

From what I can see it will not work on nix files, unless a specific plugin is written

Yes, though this is the status quo exactly, nobody has precise code intelligence for nix files. It's possible to dump an export of most NixOS option locations though, which we could use to start building a precise code intel system of some kind possibly. or at least put some stuff into the index usefully idk.

The other mentioned systems seem so deeply unserious that they are just ctags and one won't expect any precise code intel in them at all.

> From what I can see it will not work on nix files, unless a specific plugin is written Yes, though this is the status quo exactly, nobody has precise code intelligence for nix files. It's possible to dump an export of most NixOS option locations though, which we could use to start building a precise code intel system of some kind possibly. or at least put some stuff into the index usefully idk. The other mentioned systems seem so deeply unserious that they are just ctags and one won't expect any precise code intel in them at all.

forkpkgs codesearch #88