Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!eneevax!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.questions
Subject: Re: Flaming Escapes - a Partly Baked Idea
Message-ID: <10562@mimsy.UUCP>
Date: 7 Mar 88 21:36:40 GMT
References: <12162@brl-adm.ARPA>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 15

In article <12162@brl-adm.ARPA> PAAAAAR%CALSTATE.BITNET@cunyvm.cuny.edu writes:
>If the input fails to parse as a command in the current program,
>the program tests to see if it is a valid shell command and if and only
>if it is the program spawns a shell to obey it.

What with the vagaries of paths, shell `rc' files, aliases, and such,
the only reliable way to discover whether something is a `valid shell
command' is by issuing it.

>Copywrite:

Since you misspelled it, I deleted the rest :-) .
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris