# Per-User Customization

The end-user customization scripts are either sourced (allowing them to modify your shell environment) or run as an external program at the appropriate trigger time.

## get_env_details

Global/Local: both env name run

## premkvirtualenv

Global/Local: global name of new environment run

$WORKON_HOME/premkvirtualenv is run as an external program after the virtual environment is created but before the current environment is switched to point to the new env. The current working directory for the script is$WORKON_HOME and the name of the new environment is passed as an argument to the script.

## postmkvirtualenv

Global/Local: global none sourced

## preactivate

Global/Local: global, local environment name run

The global $WORKON_HOME/preactivate script is run before the new environment is enabled. The environment name is passed as the first argument. The local$VIRTUAL_ENV/bin/preactivate hook is run before the new environment is enabled. The environment name is passed as the first argument.

## postactivate

Global/Local: global, local none sourced

The global $WORKON_HOME/postactivate script is sourced after the new environment is enabled.$VIRTUAL_ENV refers to the new environment at the time the script runs.

This example script adds a space between the virtual environment name and your old PS1 by making use of _OLD_VIRTUAL_PS1.

PS1="(basename \"$VIRTUAL_ENV\")$_OLD_VIRTUAL_PS1"


The local $VIRTUAL_ENV/bin/postactivate script is sourced after the new environment is enabled.$VIRTUAL_ENV refers to the new environment at the time the script runs.

This example script for the PyMOTW environment changes the current working directory and the PATH variable to refer to the source tree containing the PyMOTW source.

pymotw_root=/Users/dhellmann/Documents/PyMOTW

## postrmvirtualenv

Global/Local: global environment name run

The \$WORKON_HOME/postrmvirtualenv script is run as an external program after the environment is removed. The full path to the environment directory is passed as an argument to the script.

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.