Date: Tue, 25 Jul 2000 10:09:45 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Richard Dawe cc: djgpp-workers AT delorie DOT com, Kevin Ryde , "tege AT swox DOT se" Subject: Re: Bug in bash 2.03's handling of compound commands? In-Reply-To: <397C9BA7.6047BE4F@phekda.freeserve.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Mon, 24 Jul 2000, Richard Dawe wrote: To: rich AT phekda DOT freeserve DOT co DOT uk CC: djgpp-workers AT delorie DOT com, user42 AT zip DOT com DOT au, tege AT swox DOT se In-reply-to: <397C9BA7 DOT 6047BE4F AT phekda DOT freeserve DOT co DOT uk> (message from Richard Dawe on Mon, 24 Jul 2000 20:40:23 +0100) Subject: Re: Bug in bash 2.03's handling of compound commands? Reply-to: Eli Zaretskii References: <397C9BA7 DOT 6047BE4F AT phekda DOT freeserve DOT co DOT uk> --text follows this line-- > Date: Mon, 24 Jul 2000 20:40:23 +0100 > From: Richard Dawe > > There is still a bug in the DJGPP port of bash 1.14.7 This is a known bug in the port of Bash 1.14.7: parenthesized commands didn't work correctly. That feature is tricky to emulate because the original code simply fork()'s, to have the subshell start with the same state (variables, aliases, etc.) as the parent. DJGPP doesn't have a working `fork', so making it work is not easy.