title: Git's "Bash.exe" vs "Git Bash.vbs"
body: <p>After some playing around ive noticed that some things dont work inside bash when just running the commands in bash.exe.</p>
  
  <p>The problems are to do with virtualenvwrapper. Not activating the environments correctly.</p>
  
  <pre><code>ERROR: Environment '/e/virtualenvs/test' does not contain an activate script.
  </code></pre>
  
  <p>And also not listing environments when doing <code>workon</code>. It just shows an empty list.</p>
  
  <p>But if its done in bash by launching it through "Git Bash.vbs", all the commands work fine, and the environments activate etc.</p>
  
  <p>I've tried looking at the vbs file but im not really used to vbs code and not sure what's going on. </p>
  
  <p>So I would like to know what the .vbs does to make things "work" in bash that would otherwise not work. Hopefully its not a virtulenvwrapper specific problem but a general thing that the .vbs file does to make things more compatible? </p>
  
  <p><strong>EDIT: Update</strong></p>
  
  <p>Ok, so after some more testing I have found exactly what is the trigger but I still dont now why its makes it work.</p>
  
  <p>If I launch sh.exe from gits directory I get the original broken behaviour. But running sh.exe --login and virtualenvwrapper works.</p>
  
  <p>So it should be now - What is --login doing to make things "work"</p>