Tracy No. 1 writes:

> > The basic rules we decided on -- if I remember them correctly -- are that
>  > when we're asked to save the terminal's settings,
>  > as Qedit apparently is doing,
>
>  Qedit doesn't ask Reflection to save its settings.  Qedit DOES change, for
>  example, the function key labels upon entering Visual mode.  Reflection
>  recognizes that they've been changed, and since that's a property
Reflection
>  saves, you may get the 'Save settings?' dialogue.

We don't use Qedit here and never have, so we're not particularly familiar
with the program. Nonetheless, I presume that Qedit is issuing a Esc&f0/1B
sequence when it enters and exits visual mode. These HP escape sequences save in
and restore from RAM memory (not a permanent configuration settings file) the
current configuration of the terminal when they're issued. This information is
not meant to be a permanent reconfiguration of the terminal but merely is meant
to allow the program to reset the terminal back to the way that the user had
it when the program exits from some other mode.

The mechanism is meant to be similar to a graphics state stack save that
occurs in most graphic description languages such as PostScript: a method to
reestablish the prior usage parameters.

Wirt Atmar

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *