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
When conda-env-autoactivate-mode t and opening a file in a directory containing environment.yml for the first time, the conda environment is not activated.
It appears that conda--switch-buffer-auto-activate is not being called as part of find-file.
$ emacs --version
GNU Emacs 30.0.50
Development version a470dfb7f8a0 on master branch; build date 2024-01-30.
(pkg-info-package-version 'conda)
(202407082135)
Possible fix:
Add conda--switch-buffer-auto-activate to find-file-hook.
The text was updated successfully, but these errors were encountered:
I've had success adding conda--switch-buffer-auto-activate to the window-selection-change-functions hook, which also means I can remove the advice to switch-to-buffer. Does anyone know of cases where this wouldn't work as expected?
One downside is that this does cause a lot of message spam. If we did go for this option, I'd rewrite some of the switching functions to avoid calling message quite so much (perhaps writing to a hidden debug buffer?).
When
conda-env-autoactivate-mode t
and opening a file in a directory containingenvironment.yml
for the first time, the conda environment is not activated.It appears that
conda--switch-buffer-auto-activate
is not being called as part offind-file
.$ emacs --version GNU Emacs 30.0.50 Development version a470dfb7f8a0 on master branch; build date 2024-01-30.
Possible fix:
Add
conda--switch-buffer-auto-activate
tofind-file-hook
.The text was updated successfully, but these errors were encountered: