From: Andrew Main <zefram@tao.co.uk>
To: schaefer@brasslantern.com (Bart Schaefer)
Cc: zsh-workers@math.gatech.edu
Subject: Re: zsh vs. ksh coproc redirection semantics
Date: Wed, 6 May 1998 17:52:52 +0100 (BST) [thread overview]
Message-ID: <199805061652.RAA28564@taos.demon.co.uk> (raw)
In-Reply-To: <980506090047.ZM13585@candle.brasslantern.com> from "Bart Schaefer" at May 6, 98 09:00:47 am
Bart Schaefer wrote:
>(Is anybody on zsh-workers reading this? Zefram, Zoltan, Peter?)
Yes. My current plan is to ignore the debate, and go for the full-on
zsh solution: by default, >&p and <&p act as if p were a normal file
descriptor referring to the appropriate pipe, as zsh does now; at the
drop of an option, we do whatever ksh does, if it's different.
Can someone who knows one end of a pipe from the other please experiment
with ksh and definitively state what it does? I'd like information on
pdksh, ksh88 and ksh93. If only one of them has behaviour inconsistent
with zsh then it's probably a bug and therefore not worth emulating.
-zefram
next parent reply other threads:[~1998-05-06 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <980506090047.ZM13585@candle.brasslantern.com>
1998-05-06 16:52 ` Andrew Main [this message]
1998-05-06 20:26 ` Bart Schaefer
1998-05-07 8:27 ` Andrew Main
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=199805061652.RAA28564@taos.demon.co.uk \
--to=zefram@tao.co.uk \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@math.gatech.edu \
/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).