From: Andrej Borsenkow <borsenkow.msk@sni.de>
To: Zsh workers mailing list <zsh-workers@math.gatech.edu>
Subject: BUG: set -n in interactive shell (3.0-xxx)
Date: Mon, 29 Jul 1996 10:49:44 +0400 (MOW) [thread overview]
Message-ID: <Pine.SV4.3.95.960729100930.16150B-100000@itsrm1> (raw)
Hi!
Small problem with no_exec option. If I per chance do 'set -n' in
interactive (worse, login) shell *and* ignoreeof option is set, it is no
more possible to leave the shell at all!!!
^D is rejected and logout/exit are not executed.
Probably, the option should be set only on command line (as with some
other)? What do you think?
greetings
-------------------------------------------------------------------------
Andrej Borsenkow Fax: +7 (095) 252 01 05
SNI ITS Moscow Tel: +7 (095) 252 13 88
NERV: borsenkow.msk E-Mail: borsenkow.msk@sni.de
-------------------------------------------------------------------------
next reply other threads:[~1996-07-30 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-29 6:49 Andrej Borsenkow [this message]
1996-07-31 2:40 ` Zefram
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=Pine.SV4.3.95.960729100930.16150B-100000@itsrm1 \
--to=borsenkow.msk@sni.de \
--cc=zsh-workers@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).