-
Notifications
You must be signed in to change notification settings - Fork 4
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
configure lsp #6
Comments
I'm not sure I follow, sorry. Is the behavior an issue with pylsp or with the plugin/lapce? |
Was hoping you'd figured out how to configure pylsp through this plugin's configuration file. |
It's something like this in
The language server probably expects a
|
Seems indeed that no lsp parameters specified in the plugin toml under extract from the the plugin volt.toml (i hope it was that file to edit, otherwise my bad, and i would very much know were to add these informations)
Here the list of lsp params i have set and none was taken into account. |
Unfortunately I think that came out when moving to the Volt plugin API. It might be a bit until I get a chance to look into it, but I'm open to PRs. |
should it not be solved when the PSP branch is merged ? |
With lapce 0.2.6 only autocompletion suggestion is working. There are no docstring popup, no warning etc although I have all installed. |
Passes expected structures into the pylsp initialization, but unclear how / if pylsp is interpreting those values (or if it requires a configuration change message), from reading through pylsp's -vv double-verbose logs... issue raised with pylsp.
FYI
python-lsp-black
adds that formatter to pylsp, which was the initial thing I wanted to configure. Disabling format-on-save in the normal lapce settings is another way to avoid undesired formatters.The text was updated successfully, but these errors were encountered: