Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: exec >& >(tee hello)

X-seq: zsh-workers 31186
From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxx
Subject: Re: exec >& >(tee hello)
Date: Thu, 28 Mar 2013 15:46:25 -0700
In-reply-to: <20130328215713.GA3414@redoubt.spodhuis.org>
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
References: <1364325715.29901.140661209502305.67203343@webmail.messagingengine.com> <130328084639.ZM28782@torch.brasslantern.com> <20130328215713.GA3414@redoubt.spodhuis.org>

On Thu, Mar 28, 2013 at 2:57 PM, Phil Pennock <
zsh-workers+phil.pennock@xxxxxxxxxxxx> wrote:

> Okay, now I'm confused.
>
> See, this works:
>
>   zsh -c 'exec > >(tee hello); echo foo'
>   zsh -c 'exec > >(tee hello)'
>
> It's only when you try to use >& to redirect both stdout and stderr that
> it fails/hangs.
>

> >(...) is parsed as its own syntactic element that semantically means
/connect to a process on a real pipe/.

>& >(...) is two elements, /join stdout with stderr/ and /connect to a
process on a FIFO/.  It only avoids being a syntax error because >(...) is
replaced by a file name to which >& can redirect.

So you're seeing the difference between pipe and FIFO behavior.

References:
- exec >& >(tee hello)
  - From: Anthony Heading
- Re: exec >& >(tee hello)
  - From: Bart Schaefer
- Re: exec >& >(tee hello)
  - From: Phil Pennock

Messages sorted by: Reverse Date, Date, Thread, Author