Open Simon-chevolleau opened 7 months ago
It looks like an issue with conda
itself -- can you show the output of conda -V
in your terminal?
Here is my versions:
I have a similar error. I think it's unrelated to conda.el.
version<("4.8.3" "can't")
checks if your conda version is higher than 4.8.3 by running conda -V
in a new shell. conda.el grabs the second value, which should be the conda version. Instead, opening a new shell yields an error and "can't" is the second value.
Opening vterm probably shows the error that's causing the issue.
https://github.com/conda/conda/issues/13451 https://github.com/microsoft/vscode-python/issues/22752
For me it was an issue with the conda python plugin, which unsets the CONDA_PREFIX variable. Setting the CONDA_PREFIX env var fixed it for me.
Ooh, thank you for digging!—Rami Chowdhury“A mind all logic is like a knife all blade - it makes the hand bleed that uses it.” - Rabindranath TagoreOn Jan 16, 2024, at 05:03, Dennis Dollée @.***> wrote: conda/conda#13451 microsoft/vscode-python#22752 For me it was an issue with the conda python plugin, which unsets the CONDA_PREFIX variable. Setting the CONDA_PREFIX env var fixed it for me.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Expected behavior
conda-env-activate
should activate a conda environment after, interactively, selecting it.Experienced behavior
An error is returned, specifying the version 4.8.3 + a string: "can't". However, I don't fully understand from which application this version is related to.
Error
Config
Environment
OS: Ubuntu 24.04 Emacs: 29.1 Doom core: v3.0.0-pre HEAD -> master 03d692f1 2023-12-08 15:11:45 -0500 Doom modules: v23.12.0-pre HEAD -> master 03d692f1 2023-12-08 15:11:45 -0500 conda: 23.7.4 conda.el (MELPA): 20231109.219