Debugger support about neovim-flake HOT 4 CLOSED

We currently provide LSPs' cmd attribute more or less as cmd = {"${pkgs.rust-analyzer}/bin/rust-analyzer"}, which explicitly receives the LSP from nixpkgs.

(P.S: this could actually be replaced with ${lib.getExe pkgs.rust-analyzer} as long as the package provides a mainProgram attribute)

The desired behaviour in #44, from what I understand, is for the user to be able to define the cmd attribute with something like cmd = {"${cfg.lspPackage"} where lspPackage is a string or a package from pkgs, and the user would simply define cfg.lspPackage as "rust-analyzer" to use rust-analyzer from user's own PATH.

from neovim-flake.

Alright to be completely honest with you, I have zero experience with debug adapters in neovim. Combined with my sheer lack of free time, I do not think I'll be able to figure out DAP add this anytime soon.

I have, however, initialized the debugging module on the feature/nvim-debug branch. Should you want to look into it, that branch should have the most basic stuff available.

That said, I'm not going to close this issue as it's going to remain a to-do in my list until either I or someone else manages to finish it.

from neovim-flake.

alright I'll see if I can make something, but I have a question related to the language module rework, #60,

what is the intended "behaviour" for user specified lsp? I assume its supposed to work with nix develop somehow, but is it like

• user should run nix develop then nvim, or
• when inside nvim we somehow detect if the project has its own preferred lsp and use that?

from neovim-flake.

Closed by #73

from neovim-flake.