> On Nov 22, 2:41 am, John Little <john.b.lit...@gmail.com> wrote:
>
>
>
>
>
>
>
>
>
> > On Nov 22, 1:36 pm, Gary Johnson <garyj...@spocom.com> wrote:
>
> > > On 2011-11-21, John Little wrote:
>
> > > > On Nov 22, 12:13 am,Srushtiwrote:
>
> > > > > Assuming I can't find anything is there some hack-y way where I can
> > > > > override the PATH used in the shell in a vim setting so that I can
> > > > > actually get back to being able to run my tests from inside vim?
>
> > > > Sure,
>
> > > > :let $PATH = 'whatever'
>
> > > That will help only if the user's shell isn't resetting PATH when
> > > it's invoked by Vim.
>
> > Good point. Srushti, if you can find the last dot-file used by your
> > shell when it's invoked by vim, you could doctor your path there, but
> > understanding those files would enable you find where the path is
> > being tweaked.
>
> For what it's worth, I had some path problems on the Solaris machine I
> run Vim on occasionally. These turned out to be caused by my .cshrc
> being sourced a second time when running any external commands from
> Vim. I ended up fixing it by checking if my path was already set up
> before modifying it in my .cshrc, but I think the OP mentioned that
> the paths being added weren't showing up twice, as mine were.
Ben, yeah the paths weren't showing up twice, which is what made it
especially confusing.
Benjamin, I didn't even know there was a .zshenv file (although I did
have one which had some other settings). At any rate, I moved the
$PATH changes I cared about from .zshrc to .zshenv and they get
sourced twice (when I do ':!echo $PATH') which isn't super-pretty but
at least the stuff I care about comes before /usr/bin. I'll continue
to look around for who the hell is moving my $PATH, but for now I can
run tests.
Thanks all,
Srushti
--
You received this message from the "vim_use" 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
No comments:
Post a Comment