From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3455 invoked from network); 16 Aug 2001 09:37:38 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 16 Aug 2001 09:37:38 -0000 Received: (qmail 11092 invoked by alias); 16 Aug 2001 09:37:31 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15640 Received: (qmail 11081 invoked from network); 16 Aug 2001 09:37:30 -0000 To: zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: EOF exiting shell In-reply-to: "Bart Schaefer"'s message of "Thu, 16 Aug 2001 02:16:30 -0000." <1010816021631.ZM11091@candle.brasslantern.com> Date: Thu, 16 Aug 2001 10:36:53 +0100 Message-ID: <20644.997954613@csr.com> From: Peter Stephenson Bart Schaefer wrote: > An EOF generated by ^D never used to get to ZLE at all, and this was > deemed annoying because it meant you couldn't override it with a user- > defined widget. > > So 12485 changed it to be handled by zle, but then if you DON'T have a > user-defined widget, it never exits. > > I haven't checked your patch to see how it interacts with user-defined > widgets bound to the EOF character. As long as it doesn't revert us back > to the days when that wasn't possible, you can probably apply it. It works at present so that you get the EOF behaviour if the widget failed, which means returned non zero status for a builtin widget. But if the current behaviour is good enough to make sure the shell exits when the tty goes away (because the read should fail) then it's an unnecessary complication. Maybe the documentation could be reworded, since the `exit after ten EOFs' is not now the behaviour most users will see. -- Peter Stephenson Software Engineer CSR Ltd., Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070 ********************************************************************** The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. **********************************************************************