[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon Oct 29 00:34:05 1996 
Subject:XVed*MaxWindows: 4 
From:A . Sloman 
Volume-ID:961029.01 

I've now tried this, and it works very well, apart from one thing. As
REF XVED says:

        Whenever a window is to be  created for a new or existing  file,
        and there  are  already MaxWindows  windows,  the last  file  on
        vedbufferlist that currently has a  window will have its  window
        destroyed. The new window then  replaces it, in the same  screen
        position.

There should be an exception when the window created is obviously
temporary, e.g. the window created by ESC e (vedfileselect).

There may be others, e.g. other temporary menu windows.

For users defining such procedures this should be controllable by
dlocalising a pop-11 variable corresponding to MaxWindows. Is there one?

It's not mentioned in the REF file.

Aaron
PS
ENTER wordswith xved shows a large number of identifiers that don't
seem to be documented anywhere. At least they are not found by ESC h.

I have a sneaking suspicion that if a lot of them were properly
documented we could bypass a lot of that horrendous .Xdefaults stuff.