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

Pylyzer requires Erg as dependency, suggest adding this info #3433

Closed
fishBone000 opened this issue Nov 12, 2024 · 2 comments
Closed

Pylyzer requires Erg as dependency, suggest adding this info #3433

fishBone000 opened this issue Nov 12, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@fishBone000
Copy link

Description

Pylyzer needs Erg to function correctly, whose path to its binary and libs should be stored in env var $ERG_PATH:

[ERROR][2024-11-11 12:08:17] .../vim/lsp/rpc.lua:770 "rpc" "/home/fishbone/.local/share/nvim/mason/bin/pylyzer" "stderr" "\27[91m[ERR] ERG_PATH not found\27[m\n"

I can resolve this by extracting tar from Erg release to my ~/.erg, then export env var by vim.fn.setenv("ERG_PATH", vim.fn.getenv("HOME") .. "/.erg")

However no such info regarding Erg is provided in lspconfig-all. I suggest adding this, or even better, adding erg_path option to let lspconfig handle exporting the env var automatically.

@fishBone000 fishBone000 added the bug Something isn't working label Nov 12, 2024
@fishBone000
Copy link
Author

File structure of Erg tarball:

tar -tf erg-x86_64-unknown-linux-gnu.tar.gz                                                                                                                                     exit 1  47s
erg
lib/
lib/std/
lib/std/exception.er
...and more lib/ files

@justinmk
Copy link
Member

send a pr

fishBone000 added a commit to fishBone000/nvim-lspconfig that referenced this issue Nov 18, 2024
Problem: Pylyzer needs Erg as dependency, such info is missing in
configs.md
Solution: Add such info in doc, and add `ergPath` setup option
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants