zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: multios doesn't work with 2>&1
Date: Sun, 27 Oct 2013 11:27:24 -0700	[thread overview]
Message-ID: <131027112724.ZM16426@torch.brasslantern.com> (raw)
In-Reply-To: <20131027174645.6934d78d@pws-pc.ntlworld.com>

On Oct 27,  5:46pm, Peter Stephenson wrote:
} Subject: Re: multios doesn't work with 2>&1
}
} 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...

I went through "git whatchanged Src/exec.c" searching for the string
"multio" and then cross-referenced with Etc/ChangeLog-4.3.

} 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

This problem is still there after 31912.

The parent shell is in zwaitjob(), as is the shell that spawned sed.
The multio copy-input-to-output job is blocked on read of the pipe,
which is never going to close because the other two jobs are waiting.


  reply	other threads:[~2013-10-27 18:27 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
2013-10-27 18:27     ` Bart Schaefer [this message]
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=131027112724.ZM16426@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).