Path: utzoo!mnetor!uunet!nuchat!peter
From: peter@nuchat.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Re: Suggestion for 1.x
Message-ID: <822@nuchat.UUCP>
Date: 19 Mar 88 03:55:10 GMT
References: <8803130914.AA16346@jade.berkeley.edu> <795@nuchat.UUCP> <7756@agate.BERKELEY.EDU>
Organization: Public Access - Houston, Tx
Lines: 20

In article ... pete@violet.berkeley.edu (Pete Goodeve) writes:
> In article <795@nuchat.UUCP> peter@nuchat.UUCP (Peter da Silva) writes:
> >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.

Do I have to do all your thinging for you :->?

Just make that ".KEY" the marker for batch files. Nobody says that you
have to be 100% consistent. You could have a command "marker" that works
like this:

marker .key execute $*
marker #!sh shell -c $*
-- 
-- a clone of Peter (have you hugged your wolf today) da Silva  `-_-'
-- normally  ...!hoptoad!academ!uhnix1!sugar!peter                U
-- Disclaimer: These aren't mere opinions... these are *values*.