Is there a reason not to get the user's config by default if it exists?

[naupaka]

https://github.com/necaris/conda.el/blob/2af92fead0e24b9cae7d0c5b446177694fc8a77e/conda.el#L193

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))