Issue #2 resolved

hooks for all venvs

jorgevargas avatarjorgevargas created an issue

I have two (maybe 3) hooks proposals

add extra things ok venv creation (install software you will always use inside the venv pip,ipython,etc. useful for --no-site-package venvs)

add extra things on workon (set some venv specific variables common to all venvs)

add extra things on vevn delete (this i'm not sure but how about making sure the are no outstanding changes in any of the repositories inside the venv)

Here is the content of my current extra_* files. Patch with the stuff to add the hooks for them.

{{{

$ cat extra_mkvenv cd $VIRTUAL_ENV easy_install pip


}}}

{{{

$ cat extra_work

this function will overwrite the default behavior of cd to go to the root of the venv, to go to HOME use cd ~

cd () { if (( $# == 0 )) then builtin cd $VIRTUAL_ENV else builtin cd "$@" fi }

move into the venv after activated

cd

}}}

Comments (1)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.