Message-Id: <4.3.1.0.20001023205604.00b0edf0@pop5.banet.net> X-Sender: usbanet DOT farley3 AT pop5 DOT banet DOT net X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Mon, 23 Oct 2000 21:11:44 -0400 To: djgpp-workers AT delorie DOT com From: "Peter J. Farley III" Subject: Re: Bash 2.04 beta 6a In-Reply-To: <39F47A27.20049.BA7D8C@localhost> 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 05:49 PM 10/23/00 -0400, Mark E. wrote: >Hi folks, >I updated the bash binary to include a corrected manifest. I haven't >received a bug report in quite a while, so I just might make things >official soon. I may have one for you, unfortunately. I don't have a pure-bash test case yet, but in the latest bleadperl version of perl there is an error that only seems to occur under DJGPP when perl opens a piped command as a file. The code basically tries to do the following: 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. Unfortunately, my patch breaks VMS perl, where they have even more special cases and exceptions than DJGPP does. I'm having to re-work my patch to make the "\\#foo" version for DJGPP only, in case it breaks other platforms (it does *not* break on linux). Is there anything you are aware of that would make "echo #foo|" produce an empty line for the first read of the pipe? BTW, "echo \#foo|" also produces an empty first line, if that helps pin anything down. I will DL your latest beta and re-test bleadperl, just in case it's something that already got fixed. Thanks again for all your work on bash. It's been a pleasure to use. Peter --------------------------------------------------------- Peter J. Farley III (pjfarley AT dorsai DOT org OR pjfarley AT banet DOT net)