On Sun, Jan 13, 2002 at 02:22:31PM -0800, Sean 'Shaleh' Perry wrote:
> right, because aterm was not a login shell and thus your rc file was ignored.
No, bash reads ~/.bashrc on a non-login shell. That's what it's FOR:
When an interactive shell that is not a login shell is
started, bash reads and executes commands from ~/.bashrc,
if that file exists.
The file ~/.profile is what only gets interpreted for a login shell.
But you gave me the pointer to a possible fix, though. The bash man page
implies that ~/.bashrc isn't read if the shell is non-interactive:
When bash is started non-interactively, to run a shell
script, for example, it looks for the variable BASH_ENV in
the environment, expands its value if it appears there,
and uses the expanded value as the name of a file to read
and execute.
Didn't catch that bit before... I'll have to play with that.
> If you simply launch a term and then run mutt by hand it would work fine.
Yeah, it always did. That's what made me so crazy. Also, if I launch a
shell and do 'aterm -e mutt' myself, then it works, and with the above, I
wouldn't expect it to. More experimentation!
--
Marc Wilson
[EMAIL PROTECTED]
[EMAIL PROTECTED]
