🚀 go-pugleaf

Jason Haar writes:

>I've thrown together a customized TPU editor (well, section file) that has
>a few keys defined/etc, but which also splits the screen into two unequal parts
>and has a help file in the bottom buffer. I do this via an initialisation file,
>but would rather get the editor to do it automagically. I've looked through the
>manual, but I can't get the CREATE_SCREEN or CREATE_BUFFER calls to do what I
>want - can a kind soul please show me how to get the following initialisation
>file into TPU format?
>
>SET RIGHT 72
>SPLIT WINDOW
>BUFF "MAIL HELP COMMANDS"
>INC FILENAME.HELP
>SET BUFF READ_ONLY
>SHRINK 5

To get the equivalent TPU statements, pass them through
the EVE parser.  For example, to translate SET RIGHT 72, enter the
following command:

Command: tpu copy_text(eve$$parse('SET RIGHT 72') + ";")

That command puts the string "eve_set_right_margin(72);" into your buffer.
Process the other commands in the same way to produce the following list of
commands:

eve_set_right_margin(72);
eve_next_window;
eve_set_right_margin(72);
eve_split_window(eve$k_no_arg);
eve_buffer("MAIL HELP COMMANDS");
eve_include_file("FILENAME.HELP");
eve_set_buffer("READ_ONLY");
eve_shrink_window(5);
eve_next_window;

You can then put them into a /COMMAND file (which is much faster than
using an /INIT file), or into your TPU$LOCAL_INIT procedure.

PS: Your code does NEXT WINDOW before it does SPLIT WINDOW, which causes
an error if executed as listed above.

Bill Robinson
DECTPU/EVE development
Digital Equipment Corporation