Message-Id: <4.3.1.0.20001027191733.00acef00@pop5.banet.net>
X-Sender: usbanet DOT farley3 AT pop5 DOT banet DOT net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Fri, 27 Oct 2000 19:23:30 -0400
To: djgpp-workers AT delorie DOT com
From: "Peter J. Farley III" <pjfarley AT banet DOT net>
Subject: Re: Bash 2.04 beta 6a
In-Reply-To: <Pine.LNX.4.10.10010271039260.17044-100000@acp3bf>
References: <4 DOT 3 DOT 1 DOT 0 DOT 20001026195212 DOT 00b2d270 AT pop5 DOT banet DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

At 10:47 AM 10/27/00 +0200, Hans-Bernhard Broeker wrote:
<Snipped>
 >Actually, I think it's the other way round. For '#' _not_ to be 
comment
 >start, Bash has to be running in interactive mode, and the 
option >allowing comments for interactive shells must be off (It's on 
by >default, IIRC).

Opps.  You're right, I misread that.  Dyslexic of me...:)

 >I.e. the only case in which I can see the original testcase behave 
like
 >the apparent expectation of the test script would be if Perl not only 

 >invoked the shell interactively, but also turned of that shell 
option,
 >deliberately.
 >
 >Either that, or the bug really is in Perl. Like, some command-line
 >preprocessing that's supposed to be done, is not. Automatic quotation 

 >of 'echo' strings beginning with a '#' or whatever might be it.
 >Without a Perl guru at hand, I have no idea what the right answer to
 >that might be.

Nor I.  But I'll try a simple test case in both environments (DJGPP and 
Linux) and see if I can produce some more info.

<Snipped>
 >Non-interactive shells will always treat # as a comment 
character. >There's not even option to switch off that behaviour.
 >
 >If there's an error regarding interactivity status, it would have to 
be >in the opposite direction.

Understood.  And thank you very much for clarifying the issue.
---------------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org OR
                      pjfarley AT banet DOT net)