From: Duncan Sinclair <Duncan.Sinclair@cis.strath.ac.uk>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: exit after 10 EOF's
Date: Sun, 19 Sep 2004 08:45:14 +0100 [thread overview]
Message-ID: <D8064C1C-0A0F-11D9-A0DD-0003931123E4@cis.strath.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0409181943300.6971@toltec.zanshin.com>
Hi Guys,
My own feelings are that this...
> However, because no one ever intended for 10 consecutive EOF
> _characters_
> to be treated as a real EOF -- rather, they intended 10 consecutive
> zero-
> byte reads to be treated as _not_ an EOF character, and nobody ever
> typed
> 10 EOF characters on purpose -- zsh does _not_ have to play dumb and
> exit
> on 10 EOF characters.
... while it may have been historically true, isn't any more. I quite
often have to use a shared account where the shell is set to tcsh, and
ignoreeof is turned on. It annoys me greatly, but as it is a shared
account I have limited power to change things. I have held down
control-D on purpose and watched a whole stream of warnings scroll up
the screen rather than give in and type "exit" or "logout" - tcsh
eventually gets the message and exits.
This is why I feel that Peter's patch isn't a bad thing. As for
default vs configured behaviour wrt widgets and such, I'd agree that if
you've set ignoreeof and you've got a special binding on <whatever EOF
is set to>, then you probably want to be able to hit it 10 times in a
row without the shell exiting.
But in the absence of any special binding I don't see what's wrong with
giving in and exiting after <some number> of the standard ignoreeof
warnings have been printed.
I believe that tcsh (30 warnings?), bash (10) and ksh (10) all do this,
and they all have the same ability to detect an EOF character
separately from an EOF condition.
Cheers,
Duncan.
next prev parent reply other threads:[~2004-09-19 7:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 11:18 Peter Stephenson
2004-09-13 17:51 ` Bart Schaefer
2004-09-15 9:46 ` Peter Stephenson
2004-09-15 15:43 ` Bart Schaefer
2004-09-15 16:02 ` Bart Schaefer
2004-09-15 16:14 ` Peter Stephenson
2004-09-16 14:57 ` Peter Stephenson
2004-09-16 16:12 ` Bart Schaefer
2004-09-16 16:28 ` Peter Stephenson
2004-09-19 6:50 ` Bart Schaefer
2004-09-19 7:45 ` Duncan Sinclair [this message]
2004-09-19 16:41 ` Bart Schaefer
2004-09-19 17:52 ` Peter Stephenson
2004-09-19 18:26 ` Bart Schaefer
2004-09-19 19:25 ` Bart Schaefer
2004-09-20 10:15 ` Peter Stephenson
2004-09-20 13:59 ` Peter Stephenson
2004-09-20 14:43 ` Bart Schaefer
2004-09-20 14:53 ` Peter Stephenson
2004-09-19 19:11 ` Bart Schaefer
2004-09-19 11:53 ` Peter Stephenson
2004-09-19 17:00 ` Bart Schaefer
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=D8064C1C-0A0F-11D9-A0DD-0003931123E4@cis.strath.ac.uk \
--to=duncan.sinclair@cis.strath.ac.uk \
--cc=zsh-workers@sunsite.dk \
/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).