Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(upstream): language servers shouldn't be launched through package managers or interpreters #7

Open
WieeRd opened this issue Oct 10, 2024 · 0 comments
Labels
upstream Not my fault

Comments

@WieeRd
Copy link
Owner

WieeRd commented Oct 10, 2024

As mentioned in #2, some servers in lspconfig are launched through package manager / language interpreter executables and not their own executables. They are blacklisted as false positives of executable availability check.

dotnet
java
nc
node
npx
perl
python
python3

I think these are against the principle of making the least assumptions about the user's system, and should be fixed in the upstream. For example, pyright can also be installed using npm / npx yet its cmd is registered as pyright. Inconsistency with rest of the node based language servers. Servers launched through python -m <server> can be installed using pipx and they will be made available to ~/.local/bin. I will work on PRs to fix server configurations like this.

@WieeRd WieeRd added the upstream Not my fault label Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Not my fault
Projects
None yet
Development

No branches or pull requests

1 participant