←back to thread

Demystifying the (Shebang): Kernel Adventures

(crocidb.com)
185 points thunderbong | 1 comments | 10 Apr 25 18:21 UTC | HN request time: 0s | source
Show context
lelandfe ◴[10 Apr 25 19:43 UTC] No.43647389[source]▶
> Since I never remember which one is which, a good way to check is using the utility `file`: `file $(which useradd)`

While we're here, can someone explain why `which` prints some locations, and for others the whole darn file? Like `which npm` prints the location; `which nvm` prints the whole darn file.

replies(5): >>43647452 #>>43647455 #>>43647461 #>>43647472 #>>43648647 #
1. awbraunstein ◴[10 Apr 25 19:51 UTC] No.43647455[source]▶
`nvm` isn't a file, it is a bash function defined in some file (likely ~/.nvm/nvm.sh). So when you say `which nvm` it prints out the definition of the `nvm` function. This is setup when you added something like:

    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
to your bashrc.