On Feb 16, 2011, at 8:52 PM, Wes Baker wrote:

> Ben,
> 
> I'm using zsh and I'm using oh-my-zsh to set everything. As part of
> the package, I have this line:
> 
>    export PATH=/usr/local/Cellar/python/2.7.1/bin:/usr/local/bin:
> $PATH

I had to set the path in ~/.zprofile to make it work on MacVim. Then I just 
check in ~/.zshrc if the path is already set.

> When in the terminal and I echo $PATH, I get this (edited to make it a
> bit more readable):
> 
>    /Users/wes/.rvm/gems/ruby-1.9.2-p136/bin:
>    /Users/wes/.rvm/gems/ruby-1.9.2-p136@global/bin:
>    /Users/wes/.rvm/rubies/ruby-1.9.2-p136/bin:
>    /Users/wes/.rvm/bin:
>    /usr/local/Cellar/python/2.7.1/bin:
>    /usr/local/bin:
>    /usr/bin:/bin:
>    /usr/sbin:/sbin:
>    /usr/local/bin:
>    /usr/X11/bin
> 
> When in MacVim (using mvim) and I type !echo $PATH, I get this:
> 
>    /usr/bin:
>    /bin:
>    /usr/sbin:
>    /sbin:
>    /usr/local/bin:
>    /usr/X11/bin:
>    /Users/wes/.rvm/gems/ruby-1.9.2-p136/bin:
>    /Users/wes/.rvm/gems/ruby-1.9.2-p136@global/bin:
>    /Users/wes/.rvm/rubies/ruby-1.9.2-p136/bin:
>    /Users/wes/.rvm/bin:/usr/local/Cellar/python/2.7.1/bin
> 
> Then for a bit of added fun, when opening MacVim from the Applications
> folder, I get this:
> 
>    /usr/bin:
>    /bin:
>    /usr/sbin:
>    /sbin:
>    /usr/local/bin:
>    /usr/X11/bin
> 
> Why the differences between everything?
> 
> Wes
> 
> On Feb 16, 8:04 pm, Ben Schmidt <mail_ben_schm...@yahoo.com.au> wrote:
>> I don't think this should be a problem these days.
>> 
>> My $PATH is the same in MacVim and Terminal, and I didn't notice a
>> change when I upgraded from 10.4.x to 10.6.x either (so I didn't even
>> know about /etc/paths until I read your email, and everything has been
>> working fine).
>> 
>> So...how are you setting your $PATH for Terminal? Are you using your
>> default login shell or something else in Terminal?
>> 
>> Ben.
>> 
>> On 17/02/11 9:20 AM, Wes Baker wrote:
>> 
>> 
>> 
>>> I know folks have talked about this before, how MacVim's $PATH
>>> variable and the terminal's $PATH variable are different. One fix was
>>> a Preference in the Advanced tab that seems to have been made a
>>> default now and removed. The $PATH variables seem close now, but the
>>> order is different and that's become a problem when using ctags.
>> 
>>> Mac has a version of ctags installed at /usr/bin/ctags and I have a
>>> version installed in homebrew at /usr/local/bin/ctags. When I do a
>>> which ctags in the Terminal I get the right ctags since it /usr/local/
>>> bin occurs first in my $PATH variable, but in MacVim (since it's
>>> using /etc/paths) it prefers /usr/bin and goes with the old decrepit
>>> version of ctags.
>> 
>>> I've attempted to find a fix by manually changing the path in
>>> the .vimrc, but that hasn't done anything. Is there any other way
>>> around this?
>> 
>>> Thanks
>>> Wes
> 
> -- 
> 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

-- 
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

Reply via email to