🚀 go-pugleaf

From article <3020@blake.acs.washington.edu>, by dlarson@blake.acs.washington.edu (Dale Larson):
> 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???

There are two ways to execute a script.  One way is to give the file name
as the "FROM" argument to a new CLI, as in:
	NewCLI CON:0/0/640/200 FROM S:startup-sequence
which is in effect what happens when the system is booted.

The second way is to use the Execute command, as in:
	Execute s:startup-sequence
(or the equivalent, just typing the name of a file that has the "S" bit
set in the file protection).

The difference is that Execute looks for variables to substitute whereas
NewCLI does not.  

In article <696@jc3b21.UUCP> fgd3@jc3b21.UUCP (Fabbian G. Dufoe) writes:
>     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.

This has tripped me up many a time.  Particularly when using something like:
	run <nil: >nil: program <nil: >nil:
which looks like a request for the variable "<nil:>" to be substituted.

-- 
Joe Smith (408)922-6220 | SMTP: JMS@F74.TYMNET.COM or jms@tymix.tymnet.com
McDonnell Douglas FSCO  | UUCP: ...!{ames,pyramid}!oliveb!tymix!tardis!jms
PO Box 49019, MS-D21    | PDP-10 support: My car's license plate is "POPJ P,"
San Jose, CA 95161-9019 | narrator.device: "I didn't say that, my Amiga did!"