Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!mailrus!ames!elroy!peregrine!zardoz!dhw68k!bob
From: bob@dhw68k.cts.com (Bob Best)
Newsgroups: comp.os.minix
Subject: Re: 1.3c /bin/sh bug? + update notes
Summary: bug isolated
Keywords: minix sh bug
Message-ID: <13155@dhw68k.cts.com>
Date: 13 Oct 88 17:31:06 GMT
References: <13152@dhw68k.cts.com>
Reply-To: bob@dhw68k.cts.com (Bob Best)
Organization: Wolfskill residence; Anaheim, CA (USA)
Lines: 16

As a follow-up to my previous posting regarding the /bin/sh bug, I
have isolated the problem to the following sequence of keystrokes:

I am at the PS1 prompt and hit 'DEL', that is, generate a SIGINT.  I
receive a new PS1 prompt.  I type 'for i in ...' and RETURN, and get
'for: not found'.  It is immaterial whether I typed anything prior to hitting
'DEL'.  The same thing happens for other keywords such as while, until,
etc.  It seems that the SIGINT handler leaves the parser in an unusual
state.  In any event, this is the only sequence that seems to cause the
problem.  Hitting '@' = KILL does not cause a problem and provides a
temporary work around.

Bob
-- 
Bob Best
uucp: ...{trwrb,hplabs}!felix!dhw68k!bob	InterNet: bob@dhw68k.cts.com