Subject: Re: shell blocking ^C
To: David Laight <firstname.lastname@example.org>
From: Sean Davis <email@example.com>
Date: 10/22/2002 12:47:47
On Tue, Oct 22, 2002 at 05:36:56PM +0100, David Laight wrote:
> I think this might have been introduced by the recent vfork
> changes to /sbin/sh - OTOH it might be a bug in my local changes :-(
> Can someone please check whether the 'current' /bin/sh still
> acts on ^C at the command line (by putting out a new prompt)
> after it fails to exec a command whose path includes a '/'.
> $ ^C
> $ /fred
> /fred: not found
> $ ^C
> At this point I don't get a new prompt.
> (The ^C may, or may not be echoed.)
yep, does the same thing here, on -current (few days old since it won't
build right now)
/~\ The ASCII
\ / Ribbon Campaign Sean Davis
X Against HTML aka dive
/ \ Email!