- 07 Jan, 2015 1 commit
-
-
Jyrki Pulliainen authored
If user manually deactivates the virtualenv when using this mode, zsh will produce following error: deactivate:12: command not found: virtualenv_deactivate To avoid this, check that the VIRTUAL_ENV flag is set before trying to automatically deactivate the virtual environment. Fixes #2185
-
- 28 Nov, 2014 1 commit
-
-
benjaoming authored
Took me a while to figure this one out, and I have a default installation of virtualenvwrapper -- this is a soft fix, just put an error message. But perhaps the fix should be to use the default value `~/.virtualenvs`.
-
- 17 Mar, 2014 1 commit
-
-
Felix Laurie von Massenbach authored
Fix robbyrussell#2355.
-
- 16 Oct, 2013 1 commit
-
-
Lei Zhang authored
-
- 08 Jun, 2013 1 commit
-
-
Andrew Grangaard authored
* removes cd override by using chpwd_functions * removes subshell call to which by using $+commands array and c param expansion to find in PATH * zsh love!
-
- 21 May, 2013 1 commit
-
-
Germán M. Bravo authored
Avoid infinite `cd` loops under certain conditions. Try getting `.venv` from the current directory (not necessarily always using git)
-
- 02 Dec, 2012 1 commit
-
-
J. Randall Hunt authored
Using lazy loading for virtualenvwrapper gives a mariginal speed improvement and doesn't stop workon_cd from working. It has the undesired effect of forcing you to call certain virtualenv commands twice before they work (only once per shell instantiation).
-
- 25 Aug, 2012 2 commits
- 25 Jun, 2012 1 commit
-
-
David Barragan authored
-
- 18 Jun, 2012 1 commit
-
-
James Walker authored
-
- 09 Jun, 2012 1 commit
-
-
Jaiden Mispy authored
-