I just did a recent brand new install yesterday and I noticed that /etc/profile no
longer contains a line like:
test -f ./.bashrc . ./.bashrc
It took me a second to figure out why .bashrc wasn't getting read (I thought it
happened automatically by the shell) until I compared it to an
IIRC, if you check the archives, you should find that the behavior of
sourcing the .bashrc file in /etc/profile was discontinued in later
cygwin releases. The fact that you have it from over a year ago is
probably because the cygwin install does not overwrite files that have
been modified or
I searched the archives and found a note from Larry suggesting that I review the
archives for 12-03-2001. I did this for all of Nov, Dec, and Jan and did not find at
least two mentions of the problem as he suggested.
My question is pretty simple: is editing the /etc/profile the recommended
I believe that .bash_login, .bash_profile or .profile is the file
you're wanting to use in this instance.
man bash
{ snip }
When an interactive shell that is not a login shell is
started, bash reads and executes commands from ~/.bashrc, if
that file exists. This may be
Wow. That was allot of discussion and conjecture on this topic. Did anyone
think of looking at the GNU bash documentation before posting?
http://www.lns.cornell.edu/public/COMP/info/bash/bashref_7.html#SEC65
Seems to me this answers the question quite well about where this kind of
check is
My question is pretty simple: is editing the /etc/profile the
recommended way to get my ~/.bashrc file sourced?
I say: no.
And if not,
what is.
It should be noted that I found a message by Gary R. Van Sickle
suggesting that .bash_profile might be a better way to do things,
but this
6 matches
Mail list logo