How does bass import function from bash and why nvm need sourced every time ? about bass

[edc]

how bass import bash functions to fish when sourcing a file

Bass does not really import bash functions. When you source a bash script in bash, two things can happen:

1. the script might "launch" other programs to do something;
2. the script can alter the current bash process to change environment variables (which then get "inherited" by any programs launched by the bash process)

When you source a bash script (e.g. nvm.sh) through bass, bass creates a temporary wrapper bash script that roughly does the following when sourced:

• read all environment variables and remember them
• source the original bash script (e.g. nvm.sh)
• re-read all the environment variables and compare what variables have been changed/added/removed

Bass then launch a bash subprocess and source the above wrapper script.

Now let's look at the two things that original script (nvm.sh) wants to do:

1. the script might "launch" other programs to do something: this is not impacted.
2. the script can alter the current bash process to change environment variables: the change is only done to the bash subprocess. However, because the wrapper script monitors the change to the environment variables, the changes are then passed to Bass, and bass will replay the changes in the fish shell.

The reason you have to source nvm every time you use it is because you use nvm through its subcommands (like nvm use). Bass does not import nvm functionality to fish, so Bass still has to invoke the nvm with subcommands in a bash shell. Because Bass has to use a new bash shell subprocess to run the subcommand, it has to ask each subprocess to source nvm.sh to get the nvm functionality before running the subcommand.

Let me know if this makes sense.

[haoadoreorange]

Yes totally ! Thanks so much for the explanation ! I close the issue here (:+1: