Question on combining `eglot` + `nix` + `poetry` about emacs.d HOT 5 CLOSED

I've never had a problem with using the latter (though I recall that there was a bug with poetry in the past where poetry env info --path fails occasionally, so simply putting export PATH="$(poetry env info --path)/bin:${PATH}" in .envrc will occasionally not work). The good thing about using the direnv solution is that it sorts out the path for other tools too, e.g. black.

from emacs.d.

All you need to do is to make sure that the language server is launched in the correct virtualenv (in your case, the virtualenv created by poetry). Personally, I use direnv; see the comment on the top of init-python.el.

from emacs.d.

Hey! I've been playing with LSPs and this sort of setup recently.

A simple thing you can do is to install your LSP server, e.g. pyright, as a dev dependency inside the poetry project. Then you can use poetry run pyright as the LSP command for eglot.

There's a further trick you can use to make direnv (and therefore Emacs, assuming you use my envrc package, or the direnv package) "see" the inside of the virtual environment built by poetry: you can change your .envrc to

use_nix
direnv_load poetry run direnv dump

I have the impression this second trick sometimes confuses poetry, though, so I probably would recommend the first approach instead.

from emacs.d.

Thanks for the suggestions! I am sorry that I reply so late. It took me a long time to figure things out. Asking eglot to use poetry run pyright helps me out!

from emacs.d.

Nice, thanks for confirming.

from emacs.d.