Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Quoting in zsh -x output
- X-seq: zsh-workers 17495
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx (Zsh hackers list)
- Subject: Re: Quoting in zsh -x output
- Date: Wed, 31 Jul 2002 14:55:10 +0000
- In-reply-to: <22628.1028108534@xxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <22628.1028108534@xxxxxxx>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author