conda--config caches the parsed output of conda config --show --json. If that's wrong the first time round, there are constant weird error messages.
In my case, I was getting Wrong type argument: arrayp, nil on all conda-* functions called. Turns out conda--config contained (json-parse-error "invalid token near 'sh'" "<string>" 1 2 2). It took forever to realize was actually the cached value, not a current error...
Perhaps having conda-config similar to elpy-config to re-load and show the (cached) configuration would be a not-too-complex fix to this and similar issues?
conda--config
caches the parsed output ofconda config --show --json
. If that's wrong the first time round, there are constant weird error messages.In my case, I was getting
Wrong type argument: arrayp, nil
on allconda-*
functions called. Turns outconda--config
contained(json-parse-error "invalid token near 'sh'" "<string>" 1 2 2)
. It took forever to realize was actually the cached value, not a current error...Perhaps having
conda-config
similar toelpy-config
to re-load and show the (cached) configuration would be a not-too-complex fix to this and similar issues?