Activation¶
Here are some general recommendations for each shell. These can differ depending on the operating system, so refer to your shell documentation for details.
bash:
.bashrc,.bash_profile– sourceactivate.shdash:
.profile– sourceactivate.shksh93:
.profile– sourceactivate.shzsh:
.zshrc– sourceactivate.shfish:
~/.config/fish/config.fish– sourceactivate.fishelvish:
~/.config/elvish/rc.elv– sourceactivate.elvnushell:
~/.config/nushell/env.nu+~/.config/nushell/config.nu– sourceactivate.nupowershell:
$PROFILE– sourceactivate.ps1csh/tcsh:
.cshrc/.tcshrc– sourceactivate.csh(minimal:PATHand environment variables only)
Here is an example using activate.sh for POSIX shell configuration:
# koopa shell
# https://koopa.acidgenomics.com/
# shellcheck source=/dev/null
XDG_CONFIG_HOME="${XDG_CONFIG_HOME:-${HOME}/.config}"
if [ -f "${XDG_CONFIG_HOME}/koopa/activate.sh" ]
then
. "${XDG_CONFIG_HOME}/koopa/activate.sh"
fi
Restart the shell. Koopa should now activate automatically at login. You can verify
this with command -v koopa.
Automatic shell configuration is enabled by our dotfiles management, documented in
Dotfiles.
User-specific activation is not required for a shared koopa installation on Linux,
which writes a configuration file into /etc/profile.d/zzz-koopa.sh.