thanks, I'm digesting this.
I tend to put commands in the wrong order. isn't first parse (or would
that be 'first parse for the list?)--wouldn't that happen last? how can
I remember the correct order of things? think in reverse?
[EMAIL PROTECTED] wrote:
>
> >> caveman: first parse copy find/last read %christmas.r "cons" none
> == "cons"
> >> caveman
> == "cons"
>
> To understand how this works, try
> >> s: find/last read %christmas.r "cons"
> s will refer to the entire text with the index pointing to the last "cons",
> actually to "{cons"
> 'copy, as someone else pointed out earlier, gets rid of the text before the
> index point and includes only the text following it.
> 'parse -------- none returns a block of individual words as strings,
> eliminating the leading "{"
> 'first gets the first word in that block.
>
>
--
-t
