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

Re: I/O to shell function in zsh coproc

X-seq: zsh-workers 28713
From: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
To: Zsh Hackers' List <zsh-workers@xxxxxxx>
Subject: Re: I/O to shell function in zsh coproc
Date: Sun, 6 Feb 2011 19:00:51 +0000
In-reply-to: <110205100816.ZM26346@torch.brasslantern.com>
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: <alpine.DEB.2.00.1102051117470.6077@MyComp2.rgm-web.net> <110205100816.ZM26346@torch.brasslantern.com>

On Sat, 05 Feb 2011 10:08:16 -0800
Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> You're right, there is a bug there.  I'm not immediately sure where to
> fix it, but there's a workaround.
> 
> The bug is that when you do 'coproc shellfunction', zsh has to fork a
> subshell to run the shellfunction in another process.  The trouble is
> that the subshell therefore gets copies of the coprocess descriptors
> that are open in the parent shell.

(More dirty washing also moved to zsh-workers.)

It's not as simple as setting FD_CLOEXEC for coproc descriptors, then?

-- 
Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/

Follow-Ups:
- Re: I/O to shell function in zsh coproc
  - From: Bart Schaefer

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