update-scripts: Add a script to search for nvim-lspconfig server packages #2393
Conversation
| @@ -0,0 +1,66 @@ | |||
| #!/usr/bin/env python3 | |||
| # This script requires nix-locate | |||
There was a problem hiding this comment.
should this be a nix shebang with nix-locate included?
There was a problem hiding this comment.
I'm not sure, I think nix-locate needs a nix-index database to be installzd
There was a problem hiding this comment.
Oh, that sounds right... I think that's why I ended up adding nix-index-database to my flake.
There was a problem hiding this comment.
I could add a dependency on https://github.com/nix-community/nix-index-database for this, but it's maybe a bit heavy?
There was a problem hiding this comment.
Yeah, I don't know if it's worth an extra input.
| @@ -13,6 +13,7 @@ | |||
| }: | |||
| lib.optionalAttrs (inputs.devshell ? flakeModule) { | |||
| devshells.default = { | |||
| packages = [ pkgs.python3 ]; | |||
|
While working on #2399 it might be nice if we can use the script to check for whether a match exists, if it doesn't automatically add it to the unpackaged list in lsp-packages.nix to make this fully automated.. |
|
Well this is the use of this script, to help search for the corresponding nixkpkgs package |
| @@ -13,6 +13,7 @@ | |||
| }: | |||
| lib.optionalAttrs (inputs.devshell ? flakeModule) { | |||
| devshells.default = { | |||
| packages = [ pkgs.python3 ]; | |||
There was a problem hiding this comment.
Any reason why you're adding python to the devshell instead of packaging your script as a derivation (like we normally do)?
| import os | ||
| import subprocess | ||
|
|
||
| repo = os.path.realpath(os.path.dirname(__file__) + "/../..") |
There was a problem hiding this comment.
Maybe this is why? I think there'd still be work-arounds, such as providing the relevant files at the CLI or via env vars. These could then be made available to the script via a wrapper or a patch/fixup phase in the drv builder.
|
@traxys friendly bump 🙂 |
This script generates a list on stdout of possible matches for nvim-lspconfig servers.
It can't easily generate something more advanced because a lot of lsp servers have false positives, for example groovy's default command is
java -jar ....., this would match thejavapackage, not the groovy language server.