Solution to issue cannot be found in the documentation.
[X] I checked the documentation.
Issue
I just installed mambaforge and ran mamba init from the Miniforge prompt. There I can switch envs via activate and the current env is shown infront of the current location. However when running Powershell I can't change the env via mamba activate env. There is no error shown but mamba info confirms that the env was not changed and it isn't just a bug with the env display. Instead I need to run conda activate in powershell.
EDIT
It seems that the mamba activate command is passed successfully to conda as
> mamba activate -h
ActivateHelp: usage: conda activate [-h] [--[no-]stack] [env_name_or_prefix]
Activate a conda environment.
Options:
positional arguments:
env_name_or_prefix The environment name or prefix to activate. If the
prefix is a relative path, it must start with './'
(or '.\' on Windows).
optional arguments:
-h, --help Show this help message and exit.
--stack Stack the environment being activated on top of the
previous active environment, rather replacing the
current active environment with a new one. Currently,
only the PATH environment variable is stacked. This
may be enabled implicitly by the 'auto_stack'
configuration variable.
--no-stack Do not stack the environment. Overrides 'auto_stack'
setting.
Solution to issue cannot be found in the documentation.
Issue
I just installed mambaforge and ran
mamba init
from the Miniforge prompt. There I can switch envs viaactivate
and the current env is shown infront of the current location. However when running Powershell I can't change the env viamamba activate env
. There is no error shown butmamba info
confirms that the env was not changed and it isn't just a bug with the env display. Instead I need to runconda activate
in powershell.EDIT
It seems that the
mamba activate
command is passed successfully to conda asInstalled packages
Environment info