Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!pdn!boake2!jc3b21!fgd3
From: fgd3@jc3b21.UUCP (Fabbian G. Dufoe)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Solution for EXECUTE: No K Directive
Message-ID: <696@jc3b21.UUCP>
Date: 31 Jul 89 22:56:47 GMT
References: <3020@blake.acs.washington.edu>
Organization: St. Petersburg Jr. College, FL
Lines: 28

From article <3020@blake.acs.washington.edu>, by dlarson@blake.acs.washington.edu (Dale Larson):
> I still do not understand two things about this problem:  First, and most
> importantly, why could I find no reference whatsoever to this error message
> in any description of EXECUTE or on any page listed under "error" in the
> index of any Amiga documentation?  (Maybe I forgot to put on my glasses :-)
> Second, why was it that I got the error message if the script was called
> from my startup-sequence, but not if it was called from the CLI the 
> startup-sequence bombed into???

     To answer your first question, the Amiga's documentation isn't very
good.  The manuals aren't organized very well for finding answers to
problems.  They're organized for reading straight through.  Even then lots
of important things are omitted and others are mentioned at the wrong time.
It would be nice to have perfect documentation, but I don't expect to see
it real soon now.

     In response to your second question I'd hazard a guess that the
offending line in the startup sequence file contained redirection of
standard input or standard output.  Execute uses the redirection symbols (<
and >) as brackets to surround parameters.  The ".bra {" and ".ket }" lines
told it to use "{" and "}" instead.

--Fabbian Dufoe
  350 Ling-A-Mor Terrace South
  St. Petersburg, Florida  33705
  813-823-2350

UUCP: ...uunet!pdn!jc3b21!fgd3