Jeremy Cantrell
Jeremy Cantrell
Do you keep all your virtualenvs in one directory? If so, `g:virtualenv_directory` needs to be set to that path. If you had it set to `~/.virtualenvs`, then calling `:VirtualEnvActivate myenv`...
Apologies for neglecting this issue. I just wanted to let you know that I agree with your confusion surrounding this. When I originally wrote this, I was using virtualenvwrapper, and...
The reason is that `sys.path` is saved prior to modification, and restored after deactivation. If another plugin or script uses the same strategy or modifies it, those changes would get...
What about this. The plugin can save the site-packages path that gets added during activation. On deactivation, remove the matching path from `sys.path` with something like `remove(index(sys_path, site_pkg))`
On linux: `["foot", "--", "vim", "{file}", "-c", "normal {line}G{column}|"]` On mac, it's a little more complicated. Luckily, if you're using iterm2, the python api saves the day. Put the following...
Was anything done with this? I'm not seeing an option that seems relevant, but this says it was completed.
This is what I ended up using in my project, and what I consider the correct application of `find`+iteration. See https://mywiki.wooledge.org/BashFAQ/001 for details. ```sh #!/usr/bin/env bash set -eu is_bash() {...
I'm assuming you mean that if `PYENV_VERSION` is set, this plugin should instead use the python version that pyenv associates with that version spec? I haven't researched what would be...
I wasn’t able to find anything in the documentation describing this behavior. Is this expected?