Article View: gnu.bash.bug
Article #998Re: always execute .bashrc
From: Noah Friedman
Date: Wed, 27 Jan 1993 02:41
Date: Wed, 27 Jan 1993 02:41
15 lines
1454 bytes
1454 bytes
In article <1993Jan25.115536.5935@thom5.ecs.ox.ac.uk> Mark.Bush@prg.ox.ac.UK (Mark Bush) writes: >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. This would be incompatible with standard bourne shell behavior. What happens if you execute a bash shell script? Even if bash were to adopt the behavior you specified, a single-letter option equivalent to `--norc' is necessary, since you can't group `--norc' with other options and the BSD #! kernel hack only allows one argument to the interpreter other than the path of the script file (which it adds implicitly).
Technical Details
Message-ID:
<FRIEDMAN.93Jan26005646@nutrimat.gnu.ai.mit.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!cis.ohio-state.edu!gnu.ai.mit.edu!friedmanReferences:
<9301141412.AA15219.SM@odin.INS.CWRU.Edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!cis.ohio-state.edu!gnu.ai.mit.edu!friedman From: friedman@gnu.ai.mit.edu (Noah Friedman) Newsgroups: gnu.bash.bug Subject: Re: always execute .bashrc Date: 26 Jan 1993 21:41:09 -0500 Organization: Free Software Foundation, 675 Mass Ave. Cambridge, MA 02139 Lines: 16 Sender: daemon@cis.ohio-state.edu Approved: bug-bash@prep.ai.mit.edu Distribution: gnu Message-ID: <FRIEDMAN.93Jan26005646@nutrimat.gnu.ai.mit.edu> References: <9301141412.AA15219.SM@odin.INS.CWRU.Edu>