Open GrigoriiTarasov opened 1 year ago
Maybe something is wrong with the detection of Git bash. You can explicitly make init
set up for bash by passing the --shell
option.
Sorry, I tried mamba init --shell
usage: mamba [-h] [-V] command ...
mamba: error: unrecognized arguments: --shell
mamba --shell
usage: mamba [-h] [-V] command ...
mamba: error: the following arguments are required: command
in git bash, what is the correct way to write it and where?
@GrigoriiTarasov
add \. "$_CONDA_ROOT/etc/profile.d/mamba.sh" || return $?
to your activate file like this(no + ,i just use diff -u to show the style
# Copyright (C) 2012 Anaconda, Inc
# SPDX-License-Identifier: BSD-3-Clause
\. "$_CONDA_ROOT/etc/profile.d/conda.sh" || return $?
+\. "$_CONDA_ROOT/etc/profile.d/mamba.sh" || return $?
conda activate "$@"
I found this problem a long time ago, and at that time I solved it by a method I didn't understand myself. But when the file was overwritten and then invalidated during a version update, I had to change the file again.
I'm surprised that people haven't really been paying attention to this problem. Maybe people prefer to use powershell on Windows? I suggest you add the word bash to the title of the issue to make it easier for people to find this place when they have problems. Or can someone explain why and then merge it into the mainline branch to fix the problem (?)
Troubleshooting docs
How did you install Mamba?
Mambaforge
Search tried in issue tracker
activate not working, init not working, name is not registered in conda env list
Latest version of Mamba
Tried in Conda?
I do not have this problem with Conda, just with Mamba
Describe your issue
In git bash
mamba activate iterstrat
mamba env list
conda env list
conda activate iterstrat
mamba info / micromamba info
Logs
~/.condarc