From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Mircea Damian <dmircea@mail.kappa.ro>,
Niall Smart <njs3@doc.ic.ac.uk>,
zsh-users@math.gatech.edu
Subject: Re: disappearing zsh's
Date: Tue, 10 Mar 1998 12:24:46 -0800 [thread overview]
Message-ID: <980310122446.ZM15156@candle.brasslantern.com> (raw)
In-Reply-To: <19980310210754.A29394@fax-hk.kappa.ro>
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
prev parent reply other threads:[~1998-03-10 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-10 18:09 Niall Smart
1998-03-10 19:07 ` Mircea Damian
1998-03-10 20:24 ` Bart Schaefer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=980310122446.ZM15156@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=dmircea@mail.kappa.ro \
--cc=njs3@doc.ic.ac.uk \
--cc=zsh-users@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).