In my example, yes, you do have to move spaces.  In your example, it is
not required because the CR terminates the command.  BUT! Sooner or later
you will get bitten by no-see-ums when passing anything significant
beyond the CR, besides it's just sloppy to do so.  I'd suggest clearing
the buffer before you fill it, if only so you really know its contents.


I still stand by my claim re efficiency of move vs string.  You're
probably correct re maximum command length; I've never had occasion to
exceed 256, which was (past tense) the limit, IIRC.  You can discover the
limit (if you're really interested) by holding down the X key while
you're at the CI prompt:  it's clearly less that 1024, looks like about
512 to me.

But again, we digress; this has nothing to do with the point of this
thread.  There are plenty of real errors in the sample code I threw
together to illustrate the point, which was,

The 2-program fix is easier AND cleaner than the one-program fix.

I'm out of here; I have a life!  Happy Friday 13.

K Tracy Pierce
Systems Programmer
Golden Gate Bridge Highway & Transportation District
San Francisco, CA  94129-0601

>Tracy,
>
>No you don't need to move spaces first. Everything after the <cr> is
>ignored. Also, the  manual says the command image has to be less the 279
>characters, but this is an old limitation. The newer limitation is much
>higher. I've successfully passed one of over 300 characters. I suspect
>it's nearer 1024 since this is the max CI variable size.
>
>John Zoltak
>North American Mfg Co
>Cleveland Ohio