Path: utzoo!attcan!uunet!husc6!bloom-beacon!apple!bionet!agate!labrea!decwrl!pyramid!oliveb!tymix!antares!jms
From: jms@antares.UUCP (joe smith)
Newsgroups: comp.sys.amiga
Subject: Assigning HERE
Keywords: "EXECUTE: No K directive"
Message-ID: <280@antares.UUCP>
Date: 24 Nov 88 04:40:21 GMT
References: <729@ardent.UUCP>
Reply-To: jms@antares.UUCP (joe smith)
Organization: Tymnet QSATS, San Jose CA
Lines: 26

In article <729@ardent.UUCP> rap@ardent.UUCP (Rob Peck) writes:
>And, from what I recall from the 1.3 documentation, there is now the
>ability to use the special character combination "$$" to represent
>the current cli number.  SO you can have more than one incantation
>(execute script) running from ICONX, each of which has the following
>line in it:
>
>   'ASSIGN HERE<$$>: ""'

I tried executing the following file, and it producted the mysterious
"EXECUTE: No K directive" message.
	.bra <
	.ket >
	ASSIGN HERE<$$>: ""
	ASSIGN

Without the ".bra" and the ".ket", it assigns the name "HERE<$$>:".  But in
order for them to work, I had to add ".key foobar" as the first line of the
file.  It looks like EXECUTE demands ".key" before it will accept bracket
substitution.  But it does work fine; HERE1: for CLI 1, HERE2: for CLI 2, etc.

-- 
+----------------------------------------------------------------------------+
| TYMNET:JMS@F29  CA:"POPJ P,"  UUCP:{ames|pyramid}oliveb!tymix!antares!jms  |
| INTERNET: (Office-1.ARPA is no more)      PHONE:Joe Smith @ (408)922-6220  |
+----------------------------------------------------------------------------+