Currently running chips is not sufficient to update the plugin system; it doesn't load the new plugins to the current fish shell which ran chips. The shell will remain unchanged.
Let's say the desired use-case scenario is that the user types chips, then the install/update takes place, and the current shell is loaded with the latest configuration and plugins. This means:
The executable file needs to call the exec* family of functions to replace itself with fish.
Fish needs to execute chips by exec chips, not just chips.
So, we need to add, at the end of the chips source code, a line that calls exec*. Then, in the build.fish file, something like below:
alias chips "exec ~/.local/bin/chips"
Alternatively, we can simply drop the line below in build.fish:
Currently running chips is not sufficient to update the plugin system; it doesn't load the new plugins to the current fish shell which ran chips. The shell will remain unchanged.
Let's say the desired use-case scenario is that the user types
chips
, then the install/update takes place, and the current shell is loaded with the latest configuration and plugins. This means:exec*
family of functions to replace itself with fish.exec chips
, not justchips
.So, we need to add, at the end of the chips source code, a line that calls
exec*
. Then, in thebuild.fish
file, something like below:Alternatively, we can simply drop the line below in
build.fish
: