Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!AUREL.CALTECH.EDU!bfox
From: bfox@AUREL.CALTECH.EDU (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: Questions/bugs.
Message-ID: <8906200300.AA00751@aurel.caltech.edu>
Date: 20 Jun 89 03:00:27 GMT
References: <89Jun19.205313edt.11770@neat.ai.toronto.edu>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: bfox@aurel.caltech.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 39


   Date: 20 Jun 89 00:51:21 GMT
   From: lamy@neat.ai.toronto.edu  (Jean-Francois Lamy)
   Organization: Department of Computer Science, University of Toronto
   References: <8906192047.AA08456@snark.bellcore.com>
   Sender: bug-bash-request@prep.ai.mit.edu

   - Will 1.00 come with a user guide?

Not one more extensive than what is currently available.  I haven't had
time to write a usable manual yet.

   - Why does 
	   if [ "$prompt" == "" ] ; then
     produce "[: too many arguments" if prompt is not defined?

Because Bash is a Bourne syntax shell, and the `[' command needs to be
written with only one `=', like:

	if [ "$PS1" = "" ]; then

   - It would be really nice if .bashrc was invoked on all shells.

~/.bashrc is sourced in all interactive shells.  Presumably, subshells,
those created with "( command )", or "shell-script", have already had
~/.bashrc sourced at a higher level.

     Just what is the order supposed to be (I can read the source, but
     I'm looking for the design rationale for init file invocation).

~/.bash_profile is sourced for each login shell.  ~/.bashrc is sourced
for each interactive shell.  If you wish to have the same commands
executed for both login and interactive startups, then explicitly
"source ~/.bashrc" in your ~/.bash_profile.  This allows you to *not*
have the same commadn executed for both login and interactive startups.

~/.bash_logout is sourced when exiting a logout shell.

Brian Fox