zsh.git/plugins/virtualenvwrapper, branch master

style: remove trailing whitespace (#12303)

2024-03-26T08:55:16Z

feat(virtualenvwrapper): run function on startup (#12163)

2024-01-18T18:34:30Z

fix(virtualenvwrapper): only deactivate if virtual env is still present (#10671)

2022-02-10T15:25:23Z

fix(virtualenvwrapper): several changes for checking git directory, including fixes (#5663)

2021-06-12T03:52:22Z

* Test only for the presence of a .git directory in virtualenvwrapper Instead of using both $(git rev-parse --show-toplevel) and a check for a .git directory, use just the latter. As well as being redundant the former does not work quite so well when using multiple worktrees; each worktree will be treated as a separate project. * Unset ENV_NAME & deactivate if no virtualenv found This addresses #4603 without breaking current behaviour (where current behaviour is correct). When changing directories, if there is no environment matching ENV_NAME, ENV_NAME is emptied and deactivate called if there is a current environment active (based on CD_VIRTUAL_ENV). * Use path comparison not string comparison for paths This will solve part of issue #4255 where WORKON_HOME is defined with a trailing slash or not normalised in some way, as well as instances where symlinks are used, and any other instances where constructed paths don't exactly match even though they go to the same file. Co-authored-by: Robby Russell

virtualenvwrapper: fix load and detection logic

2020-05-26T16:05:11Z

virtualenvwrapper: look in $HOME/.local/bin directory (#8758)

2020-03-22T12:43:58Z

virtualenvwrapper: rewrite init script location code (#8521)

2020-02-07T11:06:06Z

virtualenvwrapper: fix finding script on Ubuntu 19.10 (#8451)

2020-01-19T19:42:45Z

Change order of automatic virtualenv activation/deactivation (#6687)

2019-12-21T05:08:03Z

When navigating from a virtualenv project directory, first deactivate the virtualenv. Then, check to see if destination directory is also a virtualenv project directory. If it is activate that virtualenv. See #5817.

Use safer append to hook function arrays (#8406)

2019-11-19T17:47:12Z

Use add-zsh-hook to add functions to hooks. That way they won't be added again when doing `source ~/.zshrc` multiple times. Co-authored-by: Marc Cornellà