Paul Howarth wrote: >> It's not really clear to me what one would use . bashrc for; >> it seems everything should go in .bash_profile . > > No. The key point is that *either* .bash_profile (for login shells) > *or* .bashrc (other shells) is run, not both. See the INVOCATION section > of "man bash". Typically you would set things that are inherited by > subshells (e.g. environment variables) in .bash_profile, and things that > need to be set up in each shell (e.g. aliases) in .bashrc. OK, thanks, I am beginning to see the light. So I will put aliases in .bashrc . But is there anything else that should go there? I did look at "man bash" but found it rather dense. Am I right in thinking that bash is normally run in 3 ways: (1) The login program invokes bash as a "login shell", as also does ssh; (2) xterm, konsole, etc, invoke bash as an "interactive shell"; (3) shell scripts invoke bash as a "non-interactive shell"? -- Timothy Murphy e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
