Option on install to not add path to .profile

[muuvmuuv]

Is it possible to prevent the install-script to not add NVM to path in my e.g. ~/.profile? I use a zsh prezto plugin (node) which already does this.

[ljharb]

that already does what, invokes nvm? all the install script’s added line does is sources nvm.sh, which auto-uses the default if you have one set.

[muuvmuuv]

Yes it sources it.

ATM when I run the install script via curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash it adds this to my .zshrc:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion

I just would like to have an option to prevent that.

[ljharb]

why? that’s needed for nvm to work.

[ljharb]

Specifically I don’t know what a prezto plugin is or how it works, so perhaps explaining that would help me understand the conflict?

[muuvmuuv]

Prezto is a zsh framework like oh-my-zsh. Sorry my bad, I forgot that not everyone knew what it is.

Yes but the Prezto plugin already loads NVM, that is what I mean, so it is not needed to add it twice. The bash_completion is done by another plugin. Here is its content: https://github.com/sorin-ionescu/prezto/blob/master/modules/node/init.zsh

[ljharb]

It should be checking if the nvm function exists before sourcing nvm.sh; but i also don't understand why it makes sense for prezto to source nvm when nvm does it for you.

Either way, the install script basically only downloads $NVM_DIR, preferably with git, and then adds those lines - so if you only want nvm to exist on your system, you can always just git clone the latest tagged release.

[muuvmuuv]

Makes sense. I will also open an issue on their end to address this. I think the purpose was to keep the zshrc (or whatever) clean and let the plugin handle it.

Will do it the manual way, thank you!

[ljharb]

I'll leave this open; it's not an unreasonable request :-) it's just added complexity for what might be a very niche use case.