Open chrisburr opened 1 year ago
Any ideas how to fix this?
I'm not in a position to be able to test this out but I think the only option is something to the effect of:
PosixActivator::update_prompt(const std::string& conda_prompt_modifier)
{
- std::string ps1 = (m_env.find("PS1") != m_env.end()) ? m_env["PS1"] : "";
+ std::string ps1 = "${PS1:-}";
Yes i think that makes sense
Troubleshooting docs
How did you install Mamba?
Micromamba
Search tried in issue tracker
PS1
Latest version of Mamba
Tried in Conda?
Not applicable
Describe your issue
On some systems PS1 isn't exported and is only set as a shell variable. When calling
micromamba shell hook activate -s bash
this results in the PS1 prompt being lost when using micromamba 1.4.6. When using micromamba 1.4.2 there isn't any issue.This issue can be reproduced by running the following two lines prior to activation:
When comparing the output of
micromamba shell hook activate -s bash
I see the significat difference is at the end:I'm fairly certain the issue comes from here: https://github.com/mamba-org/mamba/blob/c926198af82a6796c67ae5eee89d903556286588/libmamba/src/core/activation.cpp#L806-L826
mamba info / micromamba info
Logs
No response
environment.yml
No response
~/.condarc
No response