[Info-vax] x86 Update 4/22/19

[hb]

On 04/28/2019 08:22 PM, Arne Vajhøj wrote:
> On 4/28/2019 1:16 PM, Phillip Helbig (undress to reply) wrote:
>>> When exiting from EVE say "yes" when it wants to save the attributes.
>>> Select a section or a TPU command file. In your LOGIN.COM, depending on
>>> the selection, define a logical TPU$SECTION or TPU$COMMAND to point to
>>> the saved file.
>>
>> I wanted to cut and paste the filename.  Regardless of TPU set mouse(x)
>> where x is on or off, it doesn't work.  OK, typed in a file name:
>>
>> DISK$USER:[HELBIG]MYSECTION.TPU$SECTION
>>                          1209
>>
>> 1209 blocks?  Really?  And binary?  Give me EDTINI.EDT any day.  :-|
> 
> That comparison is skewed.
> 
> The equivalent of EDT EDTINI (EDTINI.EDT) is EVE
> TPU$COMMAND (TPUINI.TPU).
> 
> Both are small text files.
> 
> TPU$SECTION is a binary representation of all the high level
> stuff in the editor on top of the basic TPU stuff.
> 
> The equivalent of saving a new TPU$SECTION in EDT would be more like
> creating a patched version of EDTSHR.EXE.
> 
> Arne
> 
> 
You can create your own initialization file with EVE commands. You can
create your own or let EVE create a TPU command file with TPU commands.
You can let EVE create a section file with it's current state of
procedures, variables etc.

You can have logicals or command qualifiers pointing to the command or
section files. Otherwise the command files are looked up in your current
directory or SYS$LOGIN and processed if they are found and the section
file is looked up in a system directory.

That is in your EVE command file your "set cursor bound" results in a
call to the TPU procedure "eve_set_cursor_bound" which is what you would
use/find in your TPU command file. That procedure is in the section
file, in your own or the system one: EVE$SECTION.TPU$SECTION.