On 12/11/12 2:49 PM, Greg Wooledge wrote:
> So, I'd just call it a documentation flaw. Most likely "coproc" is
> indicating whether it successfully created the coprocess (bg job), and
> you'll have to use "wait" to fetch its exit status once it becomes
> available.
More like an omission. The current documentation doesn't say anything
about what the `coproc' command returns. It only talks about what the
coprocess -- the asynchronous command -- returns.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
