zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-users@sunsite.auc.dk
Subject: Elusive coproc bug (Re: coproc tutorial (Re: questions))
Date: Tue, 5 Oct 1999 01:23:11 +0000	[thread overview]
Message-ID: <991005012311.ZM3789@candle.brasslantern.com> (raw)
In-Reply-To: <991004184232.ZM3484@candle.brasslantern.com>

On Oct 4 I wrote:
} Subject: Re: coproc tutorial (Re: questions)
}
}     coproc tr a-z A-Z
}     exec 5>&p			;: descriptor 5 is now the input of tr
}     exec 6<&p			;: descriptor 6 is now the output of tr
}     coproc sed s/DOG/CAT/ 5>&-
}     exec 7>&p			;: descriptor 7 is now the input of sed
}     exec 8<&p			;: descriptor 8 is now the output of sed
}     coproc exit		;: close p
}     cat <&6 >&7 5>&- 7>&- &	 : tr is now connected to sed
}     exec 6<&- 7>&-		;: close shell copies of descriptors
}     echo dog >&5		;: send tr some input
}     exec 5>&-			;: close 5 so tr will exit
}     cat <&8			;: should print CAT
} 
} [...] this doesn't actually work in 3.0.6, because zsh "leaks" copies of
} descriptors 5 and 7 as descriptors 13 and 14 ("strace" is your friend)

I've now completely failed to duplicate this bug both on the machine where
I first noticed it and on my machine at home, so it must depend on some
other thing that I did earlier within that same shell.  That worries me
a bit, so if any of you happen to feel like experimenting with this (or
have any idea what may be going on), I'd appreciate hearing about it.

Meanwhile, the above appears to work as expected in a freshly-started zsh
of either version series.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


      reply	other threads:[~1999-10-05  1:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-04 16:10 coproc tutorial (Re: questions) Jay Sekora
1999-10-04 18:42 ` Bart Schaefer
1999-10-05  1:23   ` 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=991005012311.ZM3789@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=zsh-users@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).