Cannot activate any env on OSX about conda.el

[SergiyKolesnikov]

I worked around this issue by setting conda-env-home-directory to the same value as conda-anaconda-home in the init.el.

I believe, the regression was introduced in 2c27196 and affects configurations with non-default conda-anaconda-home (e.g., /opt/anaconda3/ instead of the default ~/.anaconda3/).

For a non-default Anaconda path, the documentation instructs to set only conda-anaconda-home in init.el, but conda-env-home-directory still gets the default path ~/.anaconda3/ from conda-anaconda-home when the mode is initialized:

conda.el/conda.el

Lines 50 to 51 in ffafcc4

	(defcustom conda-env-home-directory conda-anaconda-home
	"Location of the directory containing the environments directory."

An easy fix would be to update the docs accordingly, but it would be nice if conda-env-home-directory were updated automatically in case only conda-anaconda-home is customized.

[necaris]

@SergiyKolesnikov since you appear to have found an underlying cause I'm reopening this to take a deeper look when I get a minute -- thank you!

[hnisonoff]

I had to change

(setq conda-env-home-directory (expand-file-name "~/anaconda3/envs")
	)

to

(setq conda-env-home-directory (expand-file-name "~/anaconda3/")
	)

[c02y]

M-x conda-env-list show no result, but in terminal conda env list show 3 envs including base env.

[sampotter]

I'm having the same problem. Any thoughts about how to fix this?

[necaris]

Sorry for the delayed response! I haven't been able to reproduce this on my Emacs on OS X, but a question: are you using the exec-path-from-shell package? And can you paste the output of the *Messages* buffer after you run conda-env-list?

[sampotter]

Hmm, problem seems to be fixed for me! I haven't tried this since my last message here, but just reinstalled conda.el, and it's also possible I'm using a new version of Emacs since then.

At the time of the problem, I was using exec-path-from-shell, in case that helps.

[necaris]

@kittipatv are you still seeing this problem?

[zjp]

I'm currently having this issue. It seems like the docs expect anaconda to be in ~/ but homebrew sticks anaconda in /usr/local/ -- I took ownership of the directory but it looks like it isn't reading the environments there.

[necaris]

@zjp thank you, that's a really helpful clue! Can you try telling conda.el where to find your Anaconda installation by setting the conda-anaconda-home customizable variable? You can set this in your .emacs / init.el with:

(custom-set-variables
 '(conda-anaconda-home "/path/to/my/Anaconda"))

Or, to update the value in your current session, try M-x customize-variable RET conda-anaconda-home RET and enter the correct path there.

Once you've done this, are you able to activate an environment?

[zjp]

I had had that variable set to /usr/local/anaconda3 (after I took ownership of the folder) -- I tried also adding /usr/local/anaconda3/envs to conda-env-home-directory but couldn't get the menu to populate.

[necaris]

@zjp any chance you can paste the contents of your *Messages* buffer after you try conda-env-activate?

[zjp]

There is no output that I can see.

[zjp]

Hmmm... I rebuilt my Emacs init file and miraculously, it now finds environments in /usr/local/anaconda3. Regrettably, I'm not sure what exactly I did or I'd state what it was to try and help the original user.

[necaris]

@zjp thank you for the update! Since two of the three people who reported the issue are reporting it's fixed now, I'm going to go ahead and close it -- @kittipatv if you are still seeing this problem please reopen!

[SergiyKolesnikov]

@necaris thanks for looking into this. Just wanted to note that this issue is not OSX specific, I am using Debian 10.

[simenojensen]

@necaris, I am having a similar problem.

These are my configs:

(use-package conda
    :config
    (setq conda-anaconda-home "/usr/local/Caskroom/miniconda")
    (setq conda-env-home-directory "/usr/local/Caskroom/miniconda")
    (conda-env-initialize-interactive-shells)
    (conda-env-initialize-eshell))

I am also using exec-path-from-shell.

M-x conda-env-list is empty
M-x conda-env-activate-path lets me choose an environment from my file directory. But when I try to M-x conda-env-activate it, I receive the following error message:

Debugger entered--Lisp error: (error "No such conda environment: ")
signal(error ("No such conda environment: "))
error("No such conda environment: %s" "")
conda-env-name-to-dir("")
conda-env-is-valid("")
conda-env-activate()
funcall-interactively(conda-env-activate)
call-interactively(conda-env-activate record nil)
command-execute(conda-env-activate record)
counsel-M-x-action("conda-env-activate")
...

[hnisonoff]

I am also having this same problem.

[ivan-krukov]

Aside, from the comments from @SergiyKolesnikov, there is an issue of how the env dirs are validated.

The conda--env-dir-is-valid function checks if the candidate directory contains bin or Scripts (on windows). It seems that those will not necessarily be contained by the environment dirs. Simply adding a bin dummy subdirectory into ~/<condapath>/envs/my-env/ makes my-env discoverable by conda-env-activate.

I think that the only subdir that a conda env should contain is conda_meta (or at least this appears to be the case on my machine.

[simenojensen]

For miniconda installed with Homebrew, this fixed the error:

(setq conda-anaconda-home "/usr/local/Caskroom/miniconda/base/")

[simenojensen]

Mac OS - Homebrew - miniconda update:
Homebrew now installs miniconda under /opt.

This works for me now:
(setq conda-anaconda-home "/opt/miniconda3/")

I had to change

(setq conda-env-home-directory (expand-file-name "~/anaconda3/envs")
	)

to

(setq conda-env-home-directory (expand-file-name "~/anaconda3/")
	)

@hnisonoff Thank you! I'd like to add that the same solution is valid under spacemacs on Ubuntu/WSL2, under dotspacemacs-configuration-layers:

(conda 
:variables
conda-anaconda-home (expand-file-name "~/anaconda3") 
conda-env-home-directory (expand-file-name "~/anaconda3"))

[necaris]

Does 335474e add enough documentation to be able to work around this issue? I'd like to close if so.

[funnell]

hi @necaris, like others here I had to set conda-env-home-directory which wasn't clear from the current README. My anaconda directory is in ~/miniconda3 and from the documentation I mistakenly thought that if my env dir was in ~/miniconda3/envs (as it is for me) then I didn't need to also set conda-env-home-directory.

[necaris]

@funnell @simenojenson @c02y are you folks still having issues, or does this work for you all now?

[necaris]

Closing as resolved since no response to my earlier question, but please reopen if necessary!