I use macvim built with python interpreter support on OS X lion for python coding. In order for omnicompletion to work with the libraries for a particular python virtualenv I would like macvim to recognize that it is opened within an activated python virtualenv. On ubuntu this works exactly like i expect it to; If I open vim in an activated virtualenv, all libs specific to that virtualenv are on python's path. This does not work in macvim when launched from the mvim shell script inside an activated virtualenv. Instead, the python path consists of the global python's libs. I know there is a way around this with some semi heavy vim-scripting, but I would prefer it if it behaves like on ubuntu. I would at least want to know why it doesn't behave that way. Any ideas are welcome.
-- You received this message from the "vim_mac" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
