You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using pyenv-mode in Spacemacs and editing local files works perfectly fine.
However, when I'm editing a remote file via TRAMP, pyenv-mode-set results in ["sytem", "/bin/bash:", "pyenv:", "command", "not", "found"]
The desired behavior would be that despite editing a file remotely, the user has the option to keep pyenv locally (where e.g. my python lsp is set up).
Any ideas? Thanks in advance!
The text was updated successfully, but these errors were encountered:
I work around this by first opening a local python file and calling pyenv-mode-set and then opening the remote file over tramp. It would be really helpful if we could set a default environment in the config, so that I can use the local pyenv for completions, formatting etc.
I'm using pyenv-mode in Spacemacs and editing local files works perfectly fine.
![2020-07-31-103815_974x348_scrot](https://user-images.githubusercontent.com/33870649/89017084-4d1af480-d309-11ea-885b-d29775e39c02.png)
However, when I'm editing a remote file via TRAMP,
pyenv-mode-set
results in ["sytem", "/bin/bash:", "pyenv:", "command", "not", "found"]The desired behavior would be that despite editing a file remotely, the user has the option to keep pyenv locally (where e.g. my python lsp is set up).
Any ideas? Thanks in advance!
The text was updated successfully, but these errors were encountered: