Add python virtualenv segment

[MichaelAquilina]

Displays the current python virtualenv in a segment if the $VIRTUAL_ENV environment variable is set.

[keybits]

I've just tested this on OS X and it works great.

[MichaelAquilina]

@agnoster any chance of merging this in?

[agnoster]

Just FYI, the style for the other prompt segments is to leave one space on either side of the text, which this doesn't seem to do - but I don't use virtual env so won't bother me ;-)

[agnoster]

Or... actually looks like the code does include spaces but it doesn't look right in the screenshot.

[MichaelAquilina]

it does :) The screenshot is out of date!

[MichaelAquilina]

Should I add something to the README about this?

[tutuca]

I've installed the latest oh-my-zsh bundle and this segment is not present, just the regular boring (virtualenv ).

[MichaelAquilina]

are you using virtualenvwrapper @tutuca ?

[tutuca]

@MichaelAquilina the tool? yes, the zsh plugin? no. Should I?

[MichaelAquilina]

@tutuca could you link to a gist of your agnoster.zsh-theme file?

If you are using antigen for example, it would be in the path:
~/.antigen/repos/https-COLON--SLASH--SLASH-github.com-SLASH-agnoster-SLASH-agnoster-zsh-theme.git/agnoster.zsh-theme

if you are not sure where it is, use find:

find ~ -name "agnoster.zsh-theme"

[tutuca]

My agnoster which is the version included in oh-my-zsh, found on ~/.oh-my-zsh/themes/agnoster.zsh-theme:
https://gist.github.com/tutuca/e50cf9108fe1e3dea8a522ac42527bec

[MichaelAquilina]

For some reason your zsh-theme is different to what I put here. Check out the prompt_virtualenv function in your gist and what is in my PR: e2371ec

[tutuca]

Maybe the version didn't make it yet into oh-my-zsh...

[MichaelAquilina]

no the version in oh-my-zsh has basically changed my function. My guess is to basically provide the option to disable my feature as it may have annoyed some users. Check what the value of $VIRTUAL_ENV_DISABLE_PROMPT is to see if it is causing this feature to be disabled.

[tutuca]

$VIRTUAL_ENV_DISABLE_PROMPT is set to empty on my config (by default).

[MichaelAquilina]

try setting that to 1

[tutuca]

Ack, now it works but it has those ugly parens:

[MichaelAquilina]

What does the output of echo $VIRTUAL_ENV give you?

[MichaelAquilina]

Also, the prompt is in the wrong location :/ I dont know what is being done there. I wonder if someone just created an alternate implementation and never noticed this one has been updated.

[tutuca]

echo $VIRTUAL_ENV is Blank also

[drorata]

I am using CONDA to manage my environment. When activating an environment, $CONDA_DEFAULT_ENV is set. How could I utilize this theme to detect the conda activated environment? Currently, I'm using powerline-shell which handles the case; check this file.

[MichaelAquilina]

I am not familiar with CONDA, but I suspect it wouldnt be hard to get working with a patch. When you activate an environment, is there an env variable that specifies what your virtualenv is pointing to?

[drorata]

Following version of prompt_virtualenv seems to do the trick.

prompt_virtualenv() {
  local env='';

  if [[ -n $VIRTUAL_ENV ]]; then
    env=$VIRTUAL_ENV
  fi

  if [[ -n $CONDA_DEFAULT_ENV ]]; then
    env=$CONDA_DEFAULT_ENV
  fi

  if [[ -n $env ]]; then
    prompt_segment green black
    print -Pn " $(basename $env) "
  fi
}

It is not optimal, because it has what I consider too much spacing before and after the environment's name.

[MichaelAquilina]

I would open a PR with that to this repo if I were you :)

[drorata]

@MichaelAquilina It seems like there's one ready... #24