> and make sure ~/.bash_profile includes:
> . ~/.bashrc
> (silly bash design decision - other shells don't need this)
Hmm. Why do you say this? I always found the distinction between
.bash_profile and .bashrc quite neat. For others, a snippet of the
applicable sections in the bash manpage:
--noprofile
Do not read either the system-wide startup file
/etc/profile or any of the personal initialization
files ~/.bash_profile, ~/.bash_login, or ~/.pro�
file. By default, bash reads these files when it
is invoked as a login shell (see INVOCATION below).
--norc
Do not read and execute the personal initialization
file ~/.bashrc if the shell is interactive. This
option is on by default if the shell is invoked as
sh.
[I used this snippet as it's a quick summary of the rather long-winded but
worthwhile invocation section.]
So, I generally put my "environment" kinds of things into .bash_profile
(what I want to keep everywhere), and then my "interface" kinds of things
into .bashrc (aliases, prompty stuff, etc).
Note that I haven't used other shells much, so I don't see any clear
benefits to not operating like this.
Gus?
- Jeff
--
Posting in Outlook Express, to see how the other half lives.
(Statistics not available.)
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
