-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Description
Checklist
- I added a descriptive title
- I searched open requests and couldn't find a duplicate
What is the idea?
I don't really understand why the conda initialize
section is placed in the .bashrc
when using conda on Linux and in the .bash_profile
when initialising conda on macOS or Windows (see here).
I created a small git blame timeline here.
@kalefranz you were responsible for adding the conda initialize block to the .bash_profile
instead of .bashrc
on macOS. Is there a reason for it?
This seems weird to me, especially since the macOS terminal sources the .bashrc
by default when executing bash
in the command line.
bash
sources the .bashrc
when executed in the interactive mode (i.e. bash -i
) and the .bash_profile
when using the login mode (i.e. bash -l
). In a regular terminal, the interactive mode is the default. See the bash man page.
Here is a small list when which rcfile gets sourced (this is the same for Ubuntu and macOS, haven't tested Windows but I suppose it's the same...):
.bashrc
gets sourced when executingbash
orbash -i
in the terminal..bash_profile
gets sourced when executingbash -l
in the terminal.- Only
.bash_profile
gets sourced when executingbash -il
Why is this needed?
No response
What should happen?
This can be confusing; therefore, we should have better documentation surrounding this behavior. Please update the documentation for this repository accordingly.
Additional Context
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status