🚀 go-pugleaf

In article <1969@van-bc.UUCP> lphillips@lpami.van-bc.UUCP (Larry Phillips) writes:
>> 3.  I would like to be able to call scripts from an application (Uedit)
>> and not wait for a reply before calling another one.  Is this possible?

>When you call a script from a program, the reply must come from the
>resident process ('REXX') itself, and that reply probably comes after the
>script called has exited.

But I want that reply to come during the execution of the script, not
after it exits.  

Here's what I'm trying to do.  Uedit saves my TeX file, and calls the
script 'texify.urexx'.  This script tells AmigaTeX to process the file,
then sends a message to Uedit that the operation succeded.
("TeXifying..." appears in the message bar.)  Since it's asynchronous,
Uedit allows me to continue editing as soon as the script is started.
Now, if TeX successfully finishes, the script sends another message to
Uedit.  ("AmigaTeX successful")  But if there's an error, the script
sends the file name, row and column of error, and Uedit dutifully jumps
to the location of the error.

The problem is, I can have the script telling Uedit to do all of these
things, and Uedit does them and sends a reply, but Uedit can't send a
message back to the script.  I would like to be able to deal with the
error message from Uedit, but since it's waiting for a message and
can't send another one, I have to flip back to the TeX window and deal
with the error there.

I can do all of this if I would execute the script from the cli using
'rx'.  Uedit and the script can then have unchecked two-way
communication.  But it won't work if Uedit calls the script.  So, is
there a way to send a reply to the program that called the script, so
the two can have two-way communication?

Thanks,


-- 
---
Eric Kennedy
ejkst@cisunx.UUCP