You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the great work on this. I am wondering why this is commented out by default. I've run into a tricky issue where org-roam requires ripgrep with pcre2 support, which isn't in the conda version of ripgrep, but it is in the homebrew version or the compiled version via cargo. So, the easy solution is to stop conda from activating the base environment by default, and then just activate a specific environment for use when working on a coding project. The way to do this is with conda config --set auto_activate_base false, which gets stored to the .condarc file.
So all is good now in a terminal, but not in GUI emacs or eshell in GUI emacs.
After some digging around, I found you have a function to read the condarc, but it's not run by default, those it seems like it probably should be?
In any event -- this isn't really a bug, but I'm wondering if there is a downside to getting the user's conda config? E.g. what might I unexpectedly break by doing this?
I've fixed my issue by adding the following to my config.org (using doom emacs with the +conda option to python).
(after! conda
(conda--get-config))
The text was updated successfully, but these errors were encountered:
@naupaka doing things the way you have -- in (after! in Doom -- should be just fine! In fact, that's the way I have it set up myself!
The reason that (conda--get-config) is commented out is that I was concerned caching the configuration at load time might mess things up, if there are environment variables or other things that need to be set first.
Thanks for letting me know! You can close this issue -- I thought adding it would help other folks find it if they are running to the same problem even if it's not a bug.
conda.el/conda.el
Line 193 in 2af92fe
Thanks for the great work on this. I am wondering why this is commented out by default. I've run into a tricky issue where org-roam requires ripgrep with pcre2 support, which isn't in the conda version of ripgrep, but it is in the homebrew version or the compiled version via cargo. So, the easy solution is to stop conda from activating the base environment by default, and then just activate a specific environment for use when working on a coding project. The way to do this is with
conda config --set auto_activate_base false
, which gets stored to the.condarc
file.So all is good now in a terminal, but not in GUI emacs or eshell in GUI emacs.
After some digging around, I found you have a function to read the condarc, but it's not run by default, those it seems like it probably should be?
In any event -- this isn't really a bug, but I'm wondering if there is a downside to getting the user's conda config? E.g. what might I unexpectedly break by doing this?
I've fixed my issue by adding the following to my config.org (using doom emacs with the +conda option to python).
The text was updated successfully, but these errors were encountered: