Issue Summary:
I'm on Windows using Git Bash in VSCode. When I open a Git Bash terminal in one specific project and try to run conda, I get the following error:
bash: /cygdrive/c/Users/tssom/anaconda3/Scripts/conda.exe: No such file or directory
Running which conda returns the correct (expected) path. However, oddly enough, if I type CONDA (in all caps), it works.
$ which python
/c/Users/tssom/anaconda3/python
In another Git repo located in the same parent directory, conda works fine using Git Bash. I am opening a new VSCode instance as that project as the directory.
I’ve also noticed that $PATH differs between these two project terminals, even though there’s nothing in either project (e.g. .bashrc, .bash_profile, .env, .vscode/settings.json) that should affect the terminal environment.
Additionally, if I use Command Prompt instead of Git Bash, conda works fine in both projects.
What I’ve Tried / Observed:
- Confirmed
which condapoints to the correct path in both projects. - Confirmed
condaworks when all caps (CONDA) in the failing project. - No startup script located in the base directory of either project
- Other project in same parent folder works as expected.
- Works in regular Command Prompt. (But this is not bash)
- I have tried a full uninstall and reinstall of VSCode, Anaconda, and GitBash
- cygdrive does not exist. I am not sure why one project expects it to be there while the other does not.
Unclear Root Cause:
- Git Bash behavior?
- VSCode terminal integration?
- Anaconda environment issue?
- Windows path casing/resolution?
Any help would be appreciated. This is driving me mad.
/cygdrive/c/Users/tssom/anaconda3/Scripts/conda.exeand change that to upper case.