\begin{Jeff Waugh}
> > 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:
[snip]
> 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).
but if bash is invoked as a login shell, it reads .bash_profile, but
*not* bashrc
with other shells (eg: tcsh), it *always* reads the .tcshrc, login
shells just read .login before that.
i can't think of a case where you would want to read .bash_profile,
but not .bashrc - thus every bash user has to add ". ~/.bashrc" to the
end of their profile.
anything that is inherited correctly i put into my .login. things that
need to be set per shell invocation (including "if interactive"
blocks) go into .tcshrc.
--
- Gus
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
