From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29856 invoked from network); 31 Jul 2002 14:55:50 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 31 Jul 2002 14:55:50 -0000 Received: (qmail 2050 invoked by alias); 31 Jul 2002 14:55:40 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 17495 Received: (qmail 2032 invoked from network); 31 Jul 2002 14:55:39 -0000 From: "Bart Schaefer" Message-Id: <1020731145510.ZM11755@candle.brasslantern.com> Date: Wed, 31 Jul 2002 14:55:10 +0000 In-Reply-To: <22628.1028108534@csr.com> Comments: In reply to Peter Stephenson "Re: Quoting in zsh -x output" (Jul 31, 10:42am) References: <22628.1028108534@csr.com> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: Quoting in zsh -x output MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jul 31, 10:42am, Peter Stephenson wrote: } Subject: Re: Quoting in zsh -x output } } Dan Nelson wrote: } > I think all bash does is check each argument for spaces, single-quotes, } > or backslashes, and then quotes and escapes that argument. } } Ah, that's a different kettle of fish entirely. I don't see any problem } including the patch. I doubt if anyone is attached to the current } ambiguous behaviour of xtrace, are they? I don't have any particular problem with the patch -- though I'm not sure it covers all possible places where trace output is produced; I haven't checked -- but I would point out that there are a whole lot of things beyond mere argument quoting that prevent zsh's xtrace output from being cut'n'paste-able. Individual commands and their arguments might be, but for almost any more complex syntactic structure you're out of luck. -- 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