nave adds itself too late in the path chain about nave HOT 6 CLOSED

This is an old issue, but it helped me discover the solution, at least for myself.

Nave's path prepending works in zsh when you set your PATH in ~/.zshenv but not if you set it in ~/.zshrc. Upon reading http://zsh.sourceforge.net/Intro/intro_3.html I discovered that ~/.zshenv is the proper place for PATH anyway. After moving my PATH assignments to ~/.zshenv, nave worked great in zsh for me.

Many people do keep their paths in ~/.zshrc, so this may help someone else.

from nave.

In your .zshrc, I guess you're setting your PATH to something? What's that line look like?

from nave.

I have several of these, but I think the main issue is that I'm prepending stuff to the PATH, rather than appending. That is mainly to ensure that I use my Homebrew-installed versions of ruby, etc., rather than the old versions that ship with OS X.

from nave.

Here's where it's doing that stuff: https://github.com/isaacs/nave/blob/master/nave.sh#L93-L127

I don't use zsh, so it's possible I'm doing something wrong. But as I read the man's, it seems like it ought to be loading your zshrc file, and THEN prepending the nave path to it. But that's not happening apparently, so it's a bug, I guess.

As a workaround, you can sniff for the NAVE environment variables, and not do the PATH prepending, or do it differently, or add PATH=${NAVEPATH}:$PATH at the end somewhere.

from nave.

@jameswomack oh, wow, thanks for that tip ❤️

You're a life saver 👼

from nave.

@jameswomack Sweet! Works for me too 👍

from nave.