From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <pws@csr.com>,
zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Shell exits on bad coproc redirection
Date: Fri, 17 Aug 2001 16:34:00 +0000 [thread overview]
Message-ID: <1010817163400.ZM14169@candle.brasslantern.com> (raw)
In-Reply-To: <2306.998064324@csr.com>
On Aug 17, 5:05pm, Peter Stephenson wrote:
} Subject: Re: Shell exits on bad coproc redirection
}
} > Sun May 18 18:57:08 1997 Zoltan Hidvegi <hzoli@cs.elte.hu>
} >
} > Do not handle SIGPIPE specially for shells with job control
^^^^^^^^^^^^^^^^^^^^^^^^^^^
[">" now quotes something different]
} > paranoia. The issue was that if a `tee' spawned by a multio exits early,
} > the parent shell will get SIGPIPE and exit, too; but that's probably not a
} > bug.
}
} Multios and coprocs are pretty similar in this respect. I'm not
} particularly attached to `probably not a bug'; I would probably trade it in
} for `seems to reflect the current intention of the code' in return for a go
} on your playstation.
If we were talking about a shell script, I'd be completely in agreement.
But Zoltan's log entry is talking about shells with job control. Why
should an interactive shell ever exit on SIGPIPE?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-08-17 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 15:42 Bart Schaefer
2001-08-17 16:05 ` Peter Stephenson
2001-08-17 16:34 ` Bart Schaefer [this message]
2001-08-23 1:34 ` Geoff Wing
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=1010817163400.ZM14169@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=pws@csr.com \
--cc=zsh-workers@sunsite.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).