From: Zefram <zefram@fysh.org>
To: schaefer@candle.brasslantern.com (Bart Schaefer)
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: 3.0.6/3.1.6: Re: All sorts of file-descriptor strangeness
Date: Mon, 11 Oct 1999 09:12:52 +0100 (BST) [thread overview]
Message-ID: <E11aaZg-00010k-00@crucigera.fysh.org> (raw)
In-Reply-To: <991010211147.ZM2563@candle.brasslantern.com> from Bart Schaefer at "Oct 10, 1999 9:11:47 pm"
Bart Schaefer wrote:
>zagzig[21] coproc tr a-z A-Z
>[1] 2510
>zagzig[22] exec 5<&p
>zagzig[23] ls -l /proc/self/fd
...
>Should descriptor 5 have been passed on to "ls" in this manner?
Yes. You explicitly opened fd 5; it should be passed on to child
processes that you create.
> In particular, I think
>it would break this:
>
> coproc foo
> bar <(baz <&p)
Ah. It probably would. The coprocess fds are more of a special case
than I realised.
-zefram
next prev parent reply other threads:[~1999-10-11 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-05 9:45 Bart Schaefer
1999-10-10 8:27 ` PATCH: 3.0.6/3.1.6: " Bart Schaefer
1999-10-10 13:35 ` Zefram
1999-10-10 15:54 ` Bart Schaefer
1999-10-10 16:39 ` PATCH: Re: PATCH: no more fd mixups Bart Schaefer
1999-10-10 17:53 ` Zefram
1999-10-10 21:11 ` PATCH: 3.0.6/3.1.6: Re: All sorts of file-descriptor strangeness Bart Schaefer
1999-10-11 8:12 ` Zefram [this message]
1999-10-10 17:41 ` Zefram
1999-10-10 14:35 PATCH: no more fd mixups Zefram
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=E11aaZg-00010k-00@crucigera.fysh.org \
--to=zefram@fysh.org \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@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).