From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27488 invoked from network); 31 Jul 2002 09:42:57 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 31 Jul 2002 09:42:57 -0000 Received: (qmail 13756 invoked by alias); 31 Jul 2002 09:42:46 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 17494 Received: (qmail 13740 invoked from network); 31 Jul 2002 09:42:45 -0000 To: zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: Quoting in zsh -x output In-reply-to: "Dan Nelson"'s message of "Tue, 30 Jul 2002 15:50:31 CDT." <20020730205031.GD95493@dan.emsphone.com> Date: Wed, 31 Jul 2002 10:42:14 +0100 Message-ID: <22628.1028108534@csr.com> From: Peter Stephenson 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. It doesn't > care what quoting the user had on the commandline: > > $ echo one\ two 'one two' "one two" > + echo 'one two' 'one two' 'one two' 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? -- Peter Stephenson Software Engineer CSR Ltd., Science Park, Milton Road, Cambridge, CB4 0WH, UK Tel: +44 (0)1223 392070 ********************************************************************** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. **********************************************************************