-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
conda-env-activate-for-buffer sets PATH to "", causing "ls" "git" "bash" to fail #145
Comments
Hi -- can you confirm what the behavior is:
|
Let me add a few more environment info:
Code that initializes conda in
|
Hmm, when I create a new environment without |
Can you show the |
|
@necaris |
@espentrydal Does this behave the same as @guicho271828 above -- can you try the same debugging steps? |
@necaris Thank you for your swift reply. Sure: From
( This is after the first activation of the conda environment EDIT add: The second activation can be the same or another environment. Killing the buffer after the first activation and then opening it again does not help, I have to restart emacs to be able to activate a second conda environment. |
Dear @necaris, First of all, a big thank you for your great package! I am also able to reproduce the same issue, systematically. This causes a call to:
And to return the empty string "", which is then used to set PATH and exec-path. Here is the stack trace when using debug-on-entry on function conda-env-activate-path:
So, it seems in that situation, the conda env detected for the commit message buffer is "/", and systematically produces the command: You might have a look at how I personnally addressed the issue in branch fix_improvements_yd of my fork dizzyyogi/conda.el. Kind regards |
After activating a conda env, emacs starts failing to resolve external program, such as git or ls, in exchange to giving me the ability to M-. into the libraries in the environment.
Before activating the environment: Result of M-: (getenv "PATH")
After: Result of M-: (getenv "PATH")
Magit fails
Dired fails
Can't run anything from shell-mode buffer
I worried about my config-vars but this does not show anything suspicious
The text was updated successfully, but these errors were encountered: