🚀 go-pugleaf

As it appears that many people didn't quite understand my original
post, here is some clarification:

In article <1992Nov16.221022.67@dymaxion.ns.ca>, bg@dymaxion.ns.ca writes:
> Would someone please post a patch to the EVE routines which will
> prevent informational messages from being displayed in the messages
> window for settings saved via the "SAVE EXTENDED EVE" command.  They
> really bug me.

I'm talking about the following messages:


Default select behavior is now active.
Box operations will now overstrike your buffer.
The cursor is now bound to the flow of your text.
Default command file is undefined.
Default section file is undefined.
Editor will not check for modified attributes on exit.
Pending delete disabled.
Prompting for section file enabled.
Tab mode set to insert a TAB character.
Tabs will no longer be visible.

All of these messages flash by rapidly (or not so rapidly at 2400
baud) at the beginning of an editing session which uses my saved
section file.  The messages are annoying and furthermore obilterate
any useful messages which may have been displayed at the start of
the session, like:

Editing new file.  Could not find: BG.TMP

The procedure which creates my new section file looks like this:

	SET KEYPAD EDT
	SET CURSOR BOUND
	SET NOEXIT ATTRIBUTE CHECK
	INCLUDE DYULIB:DSPELL.TPU
	INCLUDE DYULIB:GETFRO.TPU
	INCLUDE DYULIB:FILBAR.TPU
	INCLUDE DYULIB:OUTSEL.TPU
	INCLUDE DYULIB:MARGIN.TPU

	TPU COMPILE(current_buffer)
	TPU DEFINE_KEY("dy_getfile_ronly",CTRL_G_KEY)
	TPU DEFINE_KEY("dy_getfile_ronly",KEY_NAME("G",SHIFT_KEY))
	TPU DEFINE_KEY("eve_spell",KEY_NAME("S",SHIFT_KEY))
	TPU DEFINE_KEY("vertical_bar",FS_KEY)
	TPU DEFINE_KEY("output_select",KEY_NAME("O",SHIFT_KEY))
	TPU DEFINE_KEY("tilde_bar",RS_KEY)
	TPU DEFINE_KEY("right_70",KEY_NAME("7",SHIFT_KEY))
	TPU DEFINE_KEY("right_80",KEY_NAME("8",SHIFT_KEY))

	SAVE EXTENDED EVE DYM$DISK:[DYMAX.205000]TPUEDT.NEW

I never had a problem with the extra messages appearing until
I added the lines:

	SET CURSOR BOUND
	SET NOEXIT ATTRIBUTE CHECK

Ben.
---
Ben Armstrong, Software Development                  bus: (902)422-1973
Dymaxion Research Ltd.,                              fax: (902)421-1267
Halifax, Nova Scotia, Canada B3J 1R2            Internet: bg@dymaxion.ns.ca

In article <1992Nov16.221022.67@dymaxion.ns.ca>, bg@dymaxion.ns.ca writes:
> Would someone please post a patch to the EVE routines which will
> prevent informational messages from being displayed in the messages
> window for settings saved via the "SAVE EXTENDED EVE" command.  They
> really bug me.
> 
> Ben.
> 
> P.S. Or maybe it's some hidden parameter I have to tweak.  I'm just
>      tired of all of this useless stuff flashing by every time I
>      start an editor session.
> ---
> Ben Armstrong, Software Development                  bus: (902)422-1973
> Dymaxion Research Ltd.,                              fax: (902)421-1267
> Halifax, Nova Scotia, Canada B3J 1R2            Internet: bg@dymaxion.ns.ca


I agree they are irritating. I suggest you use the eve$build tpu procedure found
in sys$examples and described in the TPU programming manuals - it requires a
little more work initially, but makes for a clean startup of eve.

Mary Trounson                    Internet:  TROUNSON@WRONZ.ORG.NZ
Computer Systems Officer         PSI:  (05301)30000047::TROUNSON
Wool Research Organisation
Christchurch                    Telephone:  (+64) (+3) 325 2421
New Zealand                           Fax:  (+64) (+3) 325 2717

In article <1992Nov18.154603.71@dymaxion.ns.ca>, bg@dymaxion.ns.ca writes:
> As it appears that many people didn't quite understand my original
> post, here is some clarification:
> 
> In article <1992Nov16.221022.67@dymaxion.ns.ca>, bg@dymaxion.ns.ca writes:
>> Would someone please post a patch to the EVE routines which will
>> prevent informational messages from being displayed in the messages
>> window for settings saved via the "SAVE EXTENDED EVE" command.  They
>> really bug me.
> 
> I'm talking about the following messages:
> 
> 
> Default select behavior is now active.
> Box operations will now overstrike your buffer.
> The cursor is now bound to the flow of your text.
> Default command file is undefined.
> Default section file is undefined.
> Editor will not check for modified attributes on exit.
> Pending delete disabled.
> Prompting for section file enabled.
> Tab mode set to insert a TAB character.
> Tabs will no longer be visible.
> 
> All of these messages flash by rapidly (or not so rapidly at 2400
> baud) at the beginning of an editing session which uses my saved
> section file.  The messages are annoying and furthermore obilterate
> any useful messages which may have been displayed at the start of
> the session, like:
> 
> Editing new file.  Could not find: BG.TMP
> 
> The procedure which creates my new section file looks like this:
> 
> 	SET KEYPAD EDT
> 	SET CURSOR BOUND
> 	SET NOEXIT ATTRIBUTE CHECK
> 	INCLUDE DYULIB:DSPELL.TPU
> 	INCLUDE DYULIB:GETFRO.TPU
> 	INCLUDE DYULIB:FILBAR.TPU
> 	INCLUDE DYULIB:OUTSEL.TPU
> 	INCLUDE DYULIB:MARGIN.TPU
> 
> 	TPU COMPILE(current_buffer)
> 	TPU DEFINE_KEY("dy_getfile_ronly",CTRL_G_KEY)
> 	TPU DEFINE_KEY("dy_getfile_ronly",KEY_NAME("G",SHIFT_KEY))
> 	TPU DEFINE_KEY("eve_spell",KEY_NAME("S",SHIFT_KEY))
> 	TPU DEFINE_KEY("vertical_bar",FS_KEY)
> 	TPU DEFINE_KEY("output_select",KEY_NAME("O",SHIFT_KEY))
> 	TPU DEFINE_KEY("tilde_bar",RS_KEY)
> 	TPU DEFINE_KEY("right_70",KEY_NAME("7",SHIFT_KEY))
> 	TPU DEFINE_KEY("right_80",KEY_NAME("8",SHIFT_KEY))
> 
> 	SAVE EXTENDED EVE DYM$DISK:[DYMAX.205000]TPUEDT.NEW
> 
> I never had a problem with the extra messages appearing until
> I added the lines:
> 
> 	SET CURSOR BOUND
> 	SET NOEXIT ATTRIBUTE CHECK
> 
> Ben.
> ---
> Ben Armstrong, Software Development                  bus: (902)422-1973
> Dymaxion Research Ltd.,                              fax: (902)421-1267
> Halifax, Nova Scotia, Canada B3J 1R2            Internet: bg@dymaxion.ns.ca


As I mentioned in a previous post the use of EVE$BUILD.TPU found in sys$examples
- documentation in VAXTPU Reference Manual Part II Appendix G is the best way to
get rid of these messages. (We used to get them with a section file which I'd
created with save extended eve - I used eve$build and the problem disappeared.)
We use similar commands, but have set them up in a command file so as to use
eve$build  eg         
.
.
.
define_key ('eve_show_buffers', key_name ('m',shift_key),
                "show_buffers",eve$x_wps_keys);
define_key ('eve_show_system_buffers', key_name ('o',shift_key),
                "show_system_buffers",eve$x_wps_keys);
.
.
.
eve_set_keypad_wps;
eve_set_cursor_free;
eve_set_noexit_attribute_check;

You will need to set up a master file  facility_MASTER.FILE  (where facility is
the name of your TPU facility) containing the names of command files you wish to
include in the section file the contents of which will appear similar to below

DYULIB:DSPELL.TPU
DYULIB:GETFRO.TPU
DYULIB:FILBAR.TPU
DYULIB:OUTSEL.TPU
DYULIB:MARGIN.TPU
DYULIB:DEFINE_KEYS.TPU

You will also need a version file facility_VERSION.DAT the contents of which are 1
line similar to that below

V05.04-000

For the set noexit attribute check you will also need, as another poster has
said, to place somewhere in an init procedure the line 

eve$$x_attr_exit_check  := false;

as until I did this no matter that I'd set noexit attribute check, on exiting
I'd always get the question about saving attibutes if I'd changed any. 

set up a symbol build 
$ BUILD == "EDIT/TPU/NODISPLAY/SECTION=SYS$SHARE:EVE$SECTION /COMMAND=SYS$EXAMPL
ES:EVE$BUILD/NOINITIALIZATION"

use the command

$ BUILD facility

you will have created your sevtion file of type tpu$section, plus a .list file
(results of the build) and a .init file (dynamically-generated code) the last 2
files can be deleted.

If you need any more help, feel free to contact me direct.

Mary Trounson                    Internet:  TROUNSON@WRONZ.ORG.NZ
Computer Systems Officer         PSI:  (05301)30000047::TROUNSON
Wool Research Organisation
Christchurch                    Telephone:  (+64) (+3) 325 2421
New Zealand                           Fax:  (+64) (+3) 325 2717