Open SimeonEhrig opened 4 years ago
Thanks! Let me check that I've understood what you're asking:
conda-env-autoactivate-mode
does the "right thing" by activating the environment if conda-project-env-name
is set (e.g. via your project- or dir-locals)conda-project-env-name
can be found for the current buffer. For example, if you switch from a Python buffer in one project to a JS buffer in another project, you would like your work in the JS buffer not to have the conda environment variables active?That seems like a reasonable feature to add. I guess it would require some rethinking of how conda-env-autoactivate-mode
is currently working -- which needs to be done anyway, because #29 is still not fixed -- so I might not get to it right away.
Yes, you understand it correct and it would be great, if you implement it.
At the moment I have a workaround with conda run -n <env_name> <command>
for my build and run commands, so it is not a show stopper. But with the workaround I have to set the path for certain tools, like company
, manually. In this case the conda-env-autoactivate-mode
would make it much easier.
Hi, nice project. Is it possible that
conda.el
automatically deactivates the conda environment if noconda-project-env-name
is activated inconda-env-autoactivate-mode
? I develop many different projects with different languages and dependencies in the same Emacs. I useprojectile
to manage the projects and I want to useconda.el
to automatically activate the right environment. But sometimes I want to edit files which are not managed byprojectile
in a clean environment so I don't have unnecessary dependencies. In this caseconda.el
should simply deactivate the environment.