Cscope as a LSP using null-ls.nvim about null-ls.nvim HOT 2 CLOSED

Your understanding is correct, though we're still missing a few pieces necessary to make something like this possible. I know absolutely nothing about cscope, but based on your description and using references as an example, the flow would be like this:

1. Neovim's LSP client sends a request for references to all attached language servers that support the method;
2. null-ls runs the command line program with the specified arguments (or reads the database, if you're able to do that through Lua / luv) and gets its output;
3. null-ls parses the output and restructures it into the correct LSP-friendly format; and
4. The null-ls handler for the method sends it back to to the LSP client, which displays it to the user.

At the moment, though, null-ls only handles diagnostics, formatting, and code actions. The main task (apart from getting and parsing cscope output) would be to build handlers for the methods we don't currently support, but the core structure should be flexible enough to handle it.

I haven't heard of anyone working on this, and I'm too ignorant about cscope to do anything myself, but I'm happy to provide full support for anyone who wants to take it on, especially since it sounds like a cool project that would really showcase what null-ls can do.

from null-ls.nvim.

Also, I don't know how much work it would take to parse the cscope output / database, but I'll also mention that I feel that this would be more appropriate as a plugin that integrates with null-ls and not something to directly include here.

from null-ls.nvim.