Message-Id:	<4.3.1.0.20001024210459.00b181f0@pop5.banet.net>
X-Sender:	usbanet DOT farley3 AT pop5 DOT banet DOT net
X-Mailer:	QUALCOMM Windows Eudora Version 4.3.1
Date:	Tue, 24 Oct 2000 21:11:08 -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
Cc:	"Mark E." <snowball3 AT bigfoot DOT com>
In-Reply-To:	<39F4D6CB.20960.364B6C@localhost>
References:	<4 DOT 3 DOT 1 DOT 0 DOT 20001023205604 DOT 00b0edf0 AT pop5 DOT banet DOT net>
	<39F47A27 DOT 20049 DOT BA7D8C AT localhost>
Mime-Version:	1.0
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

At 12:24 AM 10/24/00 -0400, Mark E. wrote:
 >> 	open a piped command as a file: "echo #foo|"
 >> 	read one line from the piped file handle
 >> 	print the results of the read
 >> 	close the file handle
 >>
 >> Well, under DJGPP "echo #foo|" produces a blank line from the first 

 >> read, rather than just "#foo".  When I patched the test to use the
 >> modified command "echo \\#foo|", then the first read got "#foo" as 
a
 >> result.
 >
 >Do you have a testcase so I can look into this?

Not just yet.  I was hoping something else might have been fixed since 
I got my copy of bash v2.04.  Mine is size 576,512, date 07-13-00 
12:43p, version info "GNU bash, version 2.04.7(1)-release 
(i386-pc-msdosdjgpp)".

If nothing rings a bell, then I will try to work up a pure bash example 
(if I can).  If I can't get bash to duplicate this behavior, I'll have 
to assume it is something else about the perl implementation and keep 
looking.

I'll get back to you as soon as I can on whether I can make bash show 
this behavior.

---------------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org OR
                      pjfarley AT banet DOT net)

- Raw text -