🚀 go-pugleaf

In response to J.Lance Wilkinson question on access to TPU and EVE procedures
from within notes:

No Notes does not document nor ship its TPU sources.  You have to hack at
things to get done what you want.

From within Notes, enter the command EVE.  Now all you have to do is start
looking at the variables that are around.

<do> tpu show (variables)
<< - show window is up - >>
<do> buffer show

Now you can scroll through the variables.  If you want to find out what type
they are and their values use the following (I used a learn sequence to do
this for each line in the file that started with Notes$):

<do> tpu message (str (get_info (notes$_user_author,"type")))

I am not sure if the EVALUATE procedure for EVE was posted to info-tpu but if
you and you have it, you could just evaluate the varaiable.

You can do the same type of thing with show (procedures).

The thing to watch out for when using your own TPU procedures inside of Notes
is for things that change the windows.  Notes does not expect this to happen
behind its back.  You can get into some really strange states (to the point of
having to ctrl/y out).

Notes, even the latest release, is based on a very old (V2.2 or V2.0) version
of EVE.  The TPU code for Notes does work with the latest version of EVE (V3.1)
(I have access to the sources and have tested it out).

My notes$command.tpu file is over 600 lines and includes code to handle mb2 and
mb3 buttons so I can do keyboard-free notes traversal (at least reading unseen
and replies, opening the next conference in my class that has an unseen
count...).  I used the procedure described above to figure out what procedures
I wanted to call.

You will like the notes$do_command TPU procedure (but that is one of the ones
that screws with the screen if you are not careful.

Have fun!

Brian J. McCarthy - DECTPU Engineering - Digital Equipment Corp.