-
-
Notifications
You must be signed in to change notification settings - Fork 66
Closed
Description
Describe the bug
See title, the same bug is mentioned here: romkatv/powerlevel10k#762
When a conda environment is activated (in my case, through Miniforge), typewritten uses $CONDA_PREFIX
Lines 56 to 57 in 69b3fad
| elif [[ ! -z $CONDA_PREFIX ]]; then | |
| tw_virtual_env="$CONDA_PREFIX" |
On the base environment, this is what I get:
CONDA_PREFIX=/home/username/.miniforge3
CONDA_DEFAULT_ENV=base
CONDA_PROMPT_MODIFIER=(base)
On environment test, this is what I get:
CONDA_PREFIX=/home/username/.miniforge3/envs/test
CONDA_DEFAULT_ENV=test
CONDA_PROMPT_MODIFIER=(test)
CONDA_PREFIX_1=/home/username/.miniforge3
On the base environment, the prefix becomes (.miniforge) instead of (base), whereas on environment test, the prefix is correctly shown as (test).
typewritten should use either CONDA_DEFAULT_ENV or CONDA_PROMPT_MODIFIER instead of CONDA_PREFIX to indicate the current conda environment.
To Reproduce
Steps to reproduce the behavior:
- Install Miniforge with
conda init - Restart shell
- See that the prefix is wrong
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels