mamba: Micromamba >v1.4.5 broken with cygwin

Troubleshooting docs

• My problem is not solved in the Troubleshooting docs

How did you install Mamba?

Micromamba

Search tried in issue tracker

yes

Latest version of Mamba

• My problem is not solved with the latest version

Tried in Conda?

Not applicable

Describe your issue

I’m using micromamba with cygwin. My .bash_profile looks like

# >>> mamba initialize >>>
# !! Contents within this block are managed by 'mamba init' !!
export MAMBA_EXE='/cygdrive/c/Users/USER/.bin/micromamba.exe';
export MAMBA_ROOT_PREFIX='/cygdrive/c/Users/USER/micromamba_prefix';
eval "$("$MAMBA_EXE" shell hook --shell bash --root-prefix "$MAMBA_ROOT_PREFIX")"
# <<< mamba initialize <<<

With micromamba <=1.4.5 shell hook --shell bash checked if !hook_source_path().empty() and if true just emitted the file shell hook without substituting $MAMBA_EXE. Only if hook_source_path() was empty would get_hook_contents be used to emit the shell hook. Crucially get_hook_contents replaced $MAMBA_EXE with the path to the binary on its own. However, this produces a broken config, as the replaced path is in windows format which cant be opened by cygwins bash. PR #2631 changed the behavior of shell hook so that get_hook_contents is always used which breaks my cygwin config.

I’m not really sure how to tackle this problem, but i think a --no-replace option for shell hook would solve my issue.

mamba info / micromamba info

No response

Logs

No response

environment.yml

No response

~/.condarc

No response