From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3712 invoked from network); 10 Mar 1998 11:33:16 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 10 Mar 1998 11:33:16 -0000 Received: (from list@localhost) by math.gatech.edu (8.8.5/8.8.5) id GAA07453; Tue, 10 Mar 1998 06:03:27 -0500 (EST) Resent-Date: Tue, 10 Mar 1998 06:03:06 -0500 (EST) Message-Id: <19980310110447.06363@bach.memex.co.uk> Date: Tue, 10 Mar 1998 11:04:47 +0000 From: Stephen Marley To: zsh-users@math.gatech.edu Subject: Re: question References: <19980309132719.A8586@fax-hk.kappa.ro> <199803091148.LAA08838@taos.demon.co.uk> <19980309180141.A4396@fax-hk.kappa.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <19980309180141.A4396@fax-hk.kappa.ro>; from Mircea Damian on Mon, Mar 09, 1998 at 06:01:41PM +0200 Resent-Message-ID: <"U-siN.0.2q1.ftH1r"@math> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/1380 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Quoting Mircea Damian (dmircea@mail.kappa.ro): > Another issue: > There is a problem in zsh-3.0.5 which I can't reproduce it. Sometimes, not > very often, it happens to exit unexpectedly from my session. It seems that > it executes the commands found in .zlogout it. Last time when I saw that my > last command was: > > > dmircea@mail:/home/dmircea% echo "somth";ls > > The output was something like: > somth > ... {ls output} ... > dmircea@mail:/home/dmircea% logout > Logout > > > > The last string("Logout") was printed by .zlogout with an echo command. > > I use zsh-3.0.5 on a Linux 2.0.33 running on a Intel P200. Any hints? This sounds suspiciously like the problem I reported a while ago when my xterm would mysteriously disappear as I typed. The was a message on the screen that I didn't have time to read but I am sure the word .zlogout was in there. I have never been able to reproduce this but it still happens very infrequently. BTW I am using an unpatched 3.0.5 on Solaris 2.6. -- stephen@memex.com