zsh uses the $PATH environment variable to find ncommands that you issue when you don't include a filepath in command. There are exceptions, such as built-ins and aliases and other stuff, but that's not important right now. And so, when you type the literal command mamba
at the command line, each directory in the $PATH variable will be searched for an executable mamba file; the first one found will be executed.
Perhaps, after your install, the mamba file was created in a directory not found in your $PATH. Consider looking for the file mamba and then adding the directory to your $PATH.
find / -name mamba 2>/dev/null
The above command searches your entire filesystem for the mamba file. Errors that it reports will be ignored 2>/dev/null
. I've done this because find
will complain about a lot of directories you don't have access to. Anyway, if find
tells you where the mamba file is, add mamba's directory to your PATH.
export PATH=$PATH:<directory-of-mamba>
It will help if you add the above line to your .zshrc as well so any new terminal sessions will also have the PATH set properly.