From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk, Alexandre Duret-Lutz <duret_g@epita.fr>
Subject: Re: xtrace and redirections
Date: Sun, 6 Feb 2000 18:24:49 +0000 [thread overview]
Message-ID: <1000206182449.ZM11053@candle.brasslantern.com> (raw)
In-Reply-To: <mvb3dr8yc28.fsf@phobos.lrde.epita.fr>
On Feb 4, 8:58pm, Alexandre Duret-Lutz wrote:
} Subject: xtrace and redirections
}
} It looks like the XTRACE output is printed after the IOs
} are redirected by the child process.
}
} This make scripts redirecting stderr fail under zsh -x.
This is, in a very round-about way, a side-effect of multios.
In order to perform multiple redirections of the same fd correctly, zsh
handles
command 2>file
in almost exactly the same way that it handles
( exec command ) 2>file
which, if you try it in another shell, produces just the effect that you
see from zsh. (All redirections are treated as if they're outside the
parens, not just stderr.)
The right fix for this appears to be that zsh should movefd(2) to a SHERR
descriptor, the same way it moves fd 0 to SHIN, and then write all xtrace
output to SHERR rather than to stderr. However, things get tricky when
you have a *real* ( ... ) or { ... } with fd 2 redirected, because in
those cases you have to reset SHERR properly in the "fake subshell" too.
I don't understand the flow through exec.c well enough to be sure of
getting that right.
Also, the xtrace code is all over the place, so this is going to be a
fairly substantial patch. Does someone else have a more elegant solution?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
prev parent reply other threads:[~2000-02-06 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-04 19:58 Alexandre Duret-Lutz
2000-02-06 18:24 ` Bart Schaefer [this message]
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=1000206182449.ZM11053@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=duret_g@epita.fr \
--cc=zsh-workers@sunsite.auc.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).