From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29688 invoked by alias); 26 Feb 2012 22:25:57 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 30273 Received: (qmail 12581 invoked from network); 26 Feb 2012 22:25:56 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at closedmail.com does not designate permitted sender hosts) From: Bart Schaefer Message-id: <120226135707.ZM18145@torch.brasslantern.com> Date: Sun, 26 Feb 2012 13:57:07 -0800 In-reply-to: <120226115220.ZM17815@torch.brasslantern.com> Comments: In reply to Bart Schaefer "Re: zsh behavior when fork() failed" (Feb 26, 11:52am) References: <120223081441.ZM2715@torch.brasslantern.com> <120224100518.ZM13322@torch.brasslantern.com> <120226115220.ZM17815@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: zsh behavior when fork() failed MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Feb 26, 11:52am, Bart Schaefer wrote: } } This also raises the question of whether a non-interactive shell should } exit on a botched "exec" (see zsh-workers/30111 and subsequent thread, } and comment on line 3364 excerpted below). Interestingly, bash does not exit on an error in exec's argument list.