Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!sunybcs!ugkamins
From: ugkamins@sunybcs.uucp (John Kaminski)
Newsgroups: comp.sys.amiga
Subject: C:Execute
Message-ID: <5129@cs.Buffalo.EDU>
Date: 9 Apr 89 23:53:07 GMT
References: <7680.AA7680@heimat>
Sender: nobody@cs.Buffalo.EDU
Reply-To: ugkamins@sunybcs.UUCP (John Kaminski)
Organization: SUNY/Buffalo Computer Science
Lines: 30

In article <7680.AA7680@heimat> sneakers@heimat.UUCP (Dan "Sneakers" Schein) writes:
[ piece chopped out ]
>   For those who did't know, "EXECUTE" looks in the S: directory automagicly.
>  So any script file in their can be started with just "EXECUTE script_file".
>  (Or "X script_file" if you rename "EXECUTE" ;-)
       ^^^                    ^^^^^^^^^^^^^^^
>
>  Sneakers
>    Dan "Sneakers" Schein            ////          BERKS AMIGA BBS
>    Sneakers Computing              ////   60+ Megs of software & messages
>    2455 McKinley Ave.      ___    ////         12/2400 Baud - 24 Hrs
>    West Lawn, PA 19609     \\\\  ////              215/678-7691
>                             \\\\////
>    {pyramid|rutgers|uunet}!cbmvax!heimat!sneakers   

I don't recommend that, at least under 1.3.  The std CLI and Shell look for
c:execute to run s:cli-startup and s:shell-startup.  I'm not real sure, but
I think the new script file-access-bit mechanism expects the same thing.
I sympathize completely, though.  I spent alotta time on a Pr1me 750, and
likewise needed a command to execute scripts (actually, it was more like
redirecting the stdin, because stuff in the file would substitute for key-
board input too).  The command was COMINPUT (COMmand INPUT), which, in its
minimum form, was CO.  So, what I did was copy execute to co.

I also hate typing in delete and a whole buncha others, so my c: looks
alot more like a UNIX /usr/bin or /bin (i.e. rm, mv, ls, cat, cp, etc.).
      //
     //
 \\ //
  \X/