From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10841 invoked from network); 10 Mar 1998 20:48:49 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 10 Mar 1998 20:48:49 -0000 Received: (from list@localhost) by math.gatech.edu (8.8.5/8.8.5) id PAA21047; Tue, 10 Mar 1998 15:24:43 -0500 (EST) Resent-Date: Tue, 10 Mar 1998 15:24:22 -0500 (EST) From: "Bart Schaefer" Message-Id: <980310122446.ZM15156@candle.brasslantern.com> Date: Tue, 10 Mar 1998 12:24:46 -0800 In-Reply-To: <19980310210754.A29394@fax-hk.kappa.ro> Comments: In reply to Mircea Damian "Re: disappearing zsh's" (Mar 10, 9:07pm) References: <19980310210754.A29394@fax-hk.kappa.ro> X-Mailer: Z-Mail (4.0b.820 20aug96) To: Mircea Damian , Niall Smart , zsh-users@math.gatech.edu Subject: Re: disappearing zsh's MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"u6SCy1.0.I85.r5Q1r"@math> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/1383 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu On Mar 10, 9:07pm, Mircea Damian wrote: } Subject: Re: disappearing zsh's } } I've got it today. My zsh exited again (without my will). This is the } output: } } -->start here<-- } Last login: Tue Mar 10 20:43:01 1998 from pop3.kappa.ro } Linux 2.0.33. } You have new mail. } } dmircea@mail:/home/dmircea% mutt } /etc/zlogout: command not found: utt } Logout } Connection to secu closed. } --> end here <-- Looks like a tty problem. There are several possibilities: 1. Zsh ought to be getting compiled with TTY_NEEDS_DRAINING defined the opposite way, but configure messed up. 2. The terminal is improperly getting set to do non-blocking reads, and the relatively new code in zsh to deal with that is still not working in all cases. 3. Some other process is still attached to your terminal and is stealing input from zsh. It may be a process that was started in some other login session, even by some other user. 4. Some combination of (2) and (3), e.g. the other process isn't stealing input, but it's messing up the terminal settings so zsh can't read it. 5. Something I haven't thought of. :-) I'd look for (3) and (4) first. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com