vim-conda is not compatible with the latest conda env activation mechanism about vim-conda HOT 5 OPEN

If you submit a pull request to fix this I will likely merge it. I don't use Conda anymore, so we should also check with: @jfishe @hstarmans @ryanfreckleton

from vim-conda.

@Nikasa1889 If you submit a PR that fixes this problem, I will merge it and make you a contributor to this repo.

from vim-conda.

I've got the same exception. It seems like if I activate the base environment by running

conda activate base

before opening vim, everything works fine. Of course, adding the old export PATH=... like @DigitalPig said also solves the problem.

I want to contribute but have never coded vimscript before, so not sure if I can do anything.

from vim-conda.

Maybe the solution would be changing the activating operation from this:

let PATH = ...

to something like this:

# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/path/to/anaconda3/bin/conda' 'shell.zsh' 'hook' 2> /dev/null)"
if [ $? -eq 0 ]; then
    eval "$__conda_setup"
else
    if [ -f "/path/to/anaconda3/etc/profile.d/conda.sh" ]; then
        . "/path/to/anaconda3/etc/profile.d/conda.sh"
    else
        export PATH="/path/to/anaconda3/bin:$PATH"
    fi
fi
unset __conda_setup
# <<< conda initialize <<<

which is the lines that conda currently puts in bashrc.

I have no experience writing vim-script. Is this going to help?

from vim-conda.

If you submit a pull request to fix this I will likely merge it. I don't use Conda anymore, so we should also check with: @jfishe @hstarmans @ryanfreckleton

Hey! Just for interesting: why don't you use conda anymore and what do you use now?

from vim-conda.