Newsgroups: gnu.bash.bug
Path: utzoo!utgpu!jarvis.csri.toronto.edu!neat.ai.toronto.edu!lamy
From: lamy@ai.utoronto.ca (Jean-Francois Lamy)
Subject: Re: Questions/bugs.
Message-ID: <89Jun19.233317edt.11745@neat.ai.toronto.edu>
Organization: Department of Computer Science, University of Toronto
References: <89Jun19.205313edt.11770@neat.ai.toronto.edu>
Distribution: gnu
Date: Mon, 19 Jun 89 23:33:13 EDT

In article <8906200300.AA00751@aurel.caltech.edu> bfox@aurel.caltech.edu writes:
>   - 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:

May I kindly suggest something like "[: '==' illegal operator" (I did say
I was editing my .cshrc :-).  And to say I'm considering switching to bash
because I spend too much time writing sh scripts. Sigh.

Jean-Francois Lamy               lamy@ai.utoronto.ca, uunet!ai.utoronto.ca!lamy
AI Group, Department of Computer Science, University of Toronto, Canada M5S 1A4