From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: multios doesn't work with 2>&1
Date: Sun, 27 Oct 2013 17:46:45 +0000 [thread overview]
Message-ID: <20131027174645.6934d78d@pws-pc.ntlworld.com> (raw)
In-Reply-To: <131027100137.ZM4100@torch.brasslantern.com>
Bart Schaefer wrote:
> If I back out workers/20666 (Jan 2005), then this example works again.
(This is really a zsh-workers thing, too, so I've moved it.)
Crikey, I'd worked out it was already broken in 2007 and I thought I was
doing well...
Playing around here, the other observation I have before looking at the
thread you're talking about is that
echo foo 2>&1 >/dev/null > >(sed 's/foo/bar/')
echo foo >/dev/null 2>&1 > >(sed 's/foo/bar/')
echo foo >/dev/null > >(sed 's/foo/bar/') 2>&1
all work as expected. This seems inconsistent --- the synchronous /
asynchronous and run-in-shell / fork behaviour is clearly different in
that case, but it's not clear that should affect redirection.
(I'd also worked out that
echo foo >/dev/null 2>&1 | sed 's/foo/bar/'
gives a different bad effect, namely you get the output you want but the
shell hangs, but that maybe another natural consequence of the thread I
haven't read yet.)
pws
next parent reply other threads:[~2013-10-27 17:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131027145917.GA5509@localhost.localdomain>
[not found] ` <131027100137.ZM4100@torch.brasslantern.com>
2013-10-27 17:46 ` Peter Stephenson [this message]
2013-10-27 18:27 ` Bart Schaefer
2013-10-27 19:39 ` Multio deadlock (Re: multios doesn't work with 2>&1) Bart Schaefer
2013-10-27 20:24 ` Bart Schaefer
2013-10-27 20:33 ` Peter Stephenson
2013-10-27 21:16 ` Peter Stephenson
2013-10-27 22:31 ` Bart Schaefer
2013-10-27 22:18 ` Bart Schaefer
2013-10-27 18:11 ` multios doesn't work with 2>&1 Bart Schaefer
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=20131027174645.6934d78d@pws-pc.ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.org \
/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).