zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Quoting in zsh -x output
Date: Wed, 31 Jul 2002 14:55:10 +0000	[thread overview]
Message-ID: <1020731145510.ZM11755@candle.brasslantern.com> (raw)
In-Reply-To: <22628.1028108534@csr.com>

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   


  reply	other threads:[~2002-07-31 14:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30 16:26 Hrvoje Niksic
2002-07-30 17:03 ` Peter Stephenson
2002-07-30 20:50   ` Dan Nelson
2002-07-31  9:42     ` Peter Stephenson
2002-07-31 14:55       ` Bart Schaefer [this message]
2002-08-03 17:05 Hrvoje Niksic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1020731145510.ZM11755@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).