From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20192 invoked by alias); 19 Apr 2012 04:38:08 -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: 30419 Received: (qmail 19009 invoked from network); 19 Apr 2012 04:38:06 -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: <120418213742.ZM6957@torch.brasslantern.com> Date: Wed, 18 Apr 2012 21:37:42 -0700 In-reply-to: <120418212700.ZM6913@torch.brasslantern.com> Comments: In reply to Bart Schaefer "Re: Follow-up: CHECK_JOBS doesn't work when only one command was run since last Control-D" (Apr 18, 9:27pm) References: <1334792501-sup-5154@pimlott.net> <120418212700.ZM6913@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers , 303623-submitter@bugs.debian.org Subject: Re: Follow-up: CHECK_JOBS doesn't work when only one command was run since last Control-D MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Apr 18, 9:27pm, Bart Schaefer wrote: } } I *think*, if we no longer care to provide this particular (mis?)feature, } that it would be OK to remove the "stopmsg = 2" from builtin.c:zexit(). } However, I'm not entirely confident there aren't other side-effects. One possible side-effect being that the shell does not "try again" when it gets a *real* EOF as opposed to reading a ctrl+d. (Events in the opposite order of my speculation in the earlier discussion in that bug track.)