I do have some PATH stuff going on in my .zshrc, but I can't imagine
that being run twice would cause any issues. If anything that should
lead to the folders showing up twice, which while not ideal shouldn't
cause any (especially these) problems.
That being said, I suspected as much as far as the PATH being modified
by someone is concerned, so I'll look some more.
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?
Thanks,
Srushti
On Nov 18, 4:01 pm, John Little <john.b.lit...@gmail.com> wrote:
> > Any idea what the cause might be?
>
> What's vim's 'shell' option set to? I suspect vim is using a
> different shell to that you expect.
>
> Otherwise, maybe some shell startup file has a line like
>
> PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:$PATH
>
> Ideally login shells should set the path, not .*rc files, but in
> practice there's often a mess, especially if you run a non-standard
> shell, or run a GUI like my KDE (I've given up trying to set the path
> applicable when .desktop files are used). If you find such a
> setting, you could put an if around it:
>
> if [[ $PATH != */usr/bin:* ]]; then
> PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:
> $PATH
> fi
>
> Regards, John
--
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