🚀 go-pugleaf

In article <m0nFPhi-0000XBC@animal.tct.com> chip@tct.COM (Chip Salzenberg) writes:
#In an earlier message to bug-bash, I wrote:
#> Chet understates the problem.  Bash runs .bashrc when you do this:
#>      bash -c 'wc' < random.file
#> Everyone (except Chet and Brian, it seems) can see that's a bug.
#
#My statement implies that Chet approves of the bug.  However, he does
#NOT approve.  Rather, he has agreed with me on several occasions that
#the behavior in question should be changed.

Not everyone thinks this is a bug!  What is wrong with the shell trying to
source .bashrc on *every* invocation (with login shell being the only
exception)?  If you specifically don't want it to read the startup file, add
a -norc flag.  If you have stuff in .bashrc which you specifically don't
want read, protect it with an `if' checking the value of PS1.

If bash works in this way, then *everyone* can get the behaviour they want
with minimum fuss.  Otherwise, how does someone who wants to make use of
their aliases and such within the environments that bash normally doesn't
source the .bashrc?

Mark