From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17774 invoked from network); 20 Jun 2001 16:51:19 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 20 Jun 2001 16:51:19 -0000 Received: (qmail 22579 invoked by alias); 20 Jun 2001 16:50:29 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14995 Received: (qmail 22533 invoked from network); 20 Jun 2001 16:50:26 -0000 From: "Bart Schaefer" Message-Id: <1010620164709.ZM8526@candle.brasslantern.com> Date: Wed, 20 Jun 2001 16:47:09 +0000 In-Reply-To: <003801c0f95e$fdc6f350$21c9ca95@mow.siemens.ru> Comments: In reply to "Andrej Borsenkow" "RE: Bug#101523: zsh segmentation fault" (Jun 20, 11:59am) References: <003801c0f95e$fdc6f350$21c9ca95@mow.siemens.ru> X-Mailer: Z-Mail (5.0.0 30July97) To: Subject: KSH_TYPESET and 4.0.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 20, 11:59am, Andrej Borsenkow wrote: } Subject: RE: Bug#101523: zsh segmentation fault } } > > local orgargs="$@" } > } > This is related to export foo=$(cmd) problem we have discussed. } > } > Did not we have some patch for it, at least in HEAD? Looks, like it should } > be in 4.0. } } 14858 Can we get a few more votes on whether KSH_TYPESET should go in 4.0.2? I note that we still haven't resolved the bash-compatibility issue. Other than that, though, I see no reason not to include it. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net