3 ms·

Have you considered a .dir-locals.el file?

• ReleaseCandidat 5y ago
  That's actually how I ended up doing it. But not dynamically running `pipenv --venv` but hard-coding the path to the virtualenv, which I don't like :(
  • bananaoomarang 5y ago
    In case it helps: I have struggled with a similar thing (poetry not pipenv, but should be applicable) and came to this working solution: https://github.com/bananaoomarang/dotfiles/blob/master/emacs/.emacs#L271-L280 https://github.com/bananaoomarang/dotfiles/blob/master/emacs... Basically: if poetry project file exists in project root, get the path for the active venv with poetry and activate with the emacs pyvenv package. This adds a little jank when switching projects I haven't looked into ironing out yet but it is functional.