-
Notifications
You must be signed in to change notification settings - Fork 37
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
Document configuration from lsp #32
Comments
Don't you mean via |
Yes, sorry, |
All but one options passed this way should work I think, depending on when the config gets updated, or is there a specific hook you want me to implement? |
Hi, A bit more specific but related to the original question: I'm currently using eglot, python-lsp and pylsp-mypy. For the built-in pylsp plugins, they can be configured according to the options listed here. I set those with the Is there a way to set pylsp-mypy options in the same place? Perhaps this is already possible, but I'm not sure how: I played around with throwing them in there, but no luck. As an alternative: would it be possible for pylsp-mypy to read a hidden configuration file, like I set these options in a directory containing a virtual environment and multiple repositories for which I use the same virtual environment, hence my wish to drop one or otherwise a few hidden config files in that directory and have everything configured for these repositories together. The current (visible) Thanks a lot! |
@kbvw I presume you are using a
|
@doolio Works like a charm. That's really helpful; many thanks! (Indeed I'm setting them in a On the original issue: it would be helpful if this route of configuration (from the client) is in the readme, since the functionality seems to be there. I guess all you need to know is A: that it's indeed possible, and B: that you have to supply the options under On the general config issue: maybe it could be unified a somewhat between the plugin and the server? For this plugin, it supports a legacy Thanks again, it works well for me now! |
Glad to hear it. I agree with having a single configuration source for all these plugins. It probably makes sense for |
I'm not sure if necro'ing this thread is the best idea, but I'm trying to get almost exactly the same thing to work, and I'm not sure what I'm doing wrong, or if the best practices have changed in the year or so since this thread was posted. Here's my
I'm pretty sure that the I'm also not sure if |
@sykloid I think you have too many parentheses. Can you try this snippet instead? ((python-mode
. ((eglot-workspace-configuration
. (:pylsp (:plugins
(:jedi
(:environment ".venv/bin/python") ; string: null (default)
:pylsp_mypy
(:overrides ["--python-executable" ".venv/bin/python" True])))))))) ; string-array: [True] (default) Edit: Note, I don't believe Curious why you don't (or do you?) include all the possible settings in your |
I agree with this. This issue should be renamed to "Document configuration from lsp" or something alike. |
Support configuration passed via didChangeDependencies method of LSP protocol.
UPD: And add information about it to documentation.
The text was updated successfully, but these errors were encountered: