🚀 go-pugleaf

In a previous article, fairfield@slacvx.slac.stanford.edu () says:

>In article <1992Sep7.023512.28308@seq.uncwil.edu>, rpowell@seq.uncwil.edu (Richard Powell) writes:
>
>    [quote deleted - irrelevant]
> 
>> Where do you find out how to write eve or lse procedures?
>
>    Start with the "VAX Text Processing Utility Manual".  This has 
>introductory chapters on the VAX TPU language, plus documentation on
>TPU built-in functions, etc.
>
>    Next, take a look at some existing TPU procedures.  I would suggest,
>with some trepidation, that you look at SYS$EXAMPLES:EVE*.TPU.  These
>comprise the _source_ of the EVE editor.  The caveat is that these files
>are quite complicated, IMHO, since at least VMS V5.3+ and the inclusion 
>of support for DECwindows.  You may do better looking at something a bit 

etc...

It seems to me from reading the postings in this group that there are 
definite conventions on writing procedures for EVE,LSE, on binding keys, on
error checking etc.   Where can one get hold of those ``conventions/rules''?

BTW, I got to say it:  LSE is definitely one great editor with all of its 
language extension capabilities.  

Now, if only TPU would allow utilities that
were spawned out to take control of the screen from time to time (like to put
up a graph on a graphics screen -- I am operating from a VT300-like terminal)
LSE would make an excellent interface to lots of other software.  (I have 
specifically in mind IDL - an interactive, plotting, data analysis language.)


  
-- 
Mirko Vukovic 
University of Wisconsin -- Madison
VUKOVIC@UWMFE.NEEP.WISC.EDU