Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!pasteur!agate!violet.berkeley.edu!pete
From: pete@violet.berkeley.edu (Pete Goodeve)
Newsgroups: comp.sys.amiga
Subject: Re: Suggestion for 1.x
Message-ID: <7756@agate.BERKELEY.EDU>
Date: 17 Mar 88 08:34:02 GMT
References: <8803130914.AA16346@jade.berkeley.edu> <795@nuchat.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Reply-To: pete@violet.berkeley.edu.UUCP (Pete Goodeve)
Organization: University of California, Berkeley
Lines: 29




In article <795@nuchat.UUCP> peter@nuchat.UUCP (Peter da Silva) writes:
>In article <8803130914.AA16346@jade.berkeley.edu>, FVEST@AUDUCVAX.BITNET writes:
>> When evaluating a command entered at the CLI prompt, before
>> returning an "Unknown command xxx" message, DOS should attempt
>                                              ^^^ You mean the CLI
>> to search the S: directory (path? :-)) and if the file is found,
>> and execute is present in the current path, the file should be
>> executed.

My CLI enhancer "Sili(Con:) already does this ...(:-))


>Almost. Actually, it should execute batch files anywhere in the path
>or the current directory without having to type "Execute".
>
...Sili(Con:) does this too (with minor restrictions).

>Even better would be one of the suggestions to look for a comment on
>the first line that indicates the processor.
>-- 

Except that Execute barfs if the script has ".KEY", and it isn't the first
line.

>-- a clone of Peter (have you hugged your wolf today) da Silva  `-_-'

					-- Pete -- (no relation...)