Accessing full binary path? #770
-
I try to keep all of the things I install for vim separate from my development environment. Using python as an example, I do this by installing npm and python black in a conda Unfortunately, in the case of it also gets a little more murky because lsp-installer controls the install, but lspconfig controls the binary name. I guess this would be easier if this repo would maintain a table of all binaries that have been installed for a server, and where they live in a more accessible fashion. maybe even a map of base-executable: full-path-executable would be nice. Just thinking out loud with that though.
as an aside, the simplest answer is to just change the cmd_env when attaching, instead of everything that i've written above... but when you do this, you actually include the development environment in the command, which is something I'd like to avoid. for reference this would just look like this
cheers and thanks for your work on this repo, it's very useful! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hello! There's no nice way of doing this currently. I've been working on a refactoring that will symlink binaries to a single, common, location (and prepend that location to the |
Beta Was this translation helpful? Give feedback.
Hello! There's no nice way of doing this currently. I've been working on a refactoring that will symlink binaries to a single, common, location (and prepend that location to the
PATH
environment of the entire neovim instance). I believe that would more or less solve your problem! Also see