🚀 go-pugleaf

Is it possible to:

1. prevent a window/buffer association from being broken

2. prevent a window size from being changed

3. prevent a window/buffer from being deleted (undisplayed)

when a new buffer is displayed?

What I may be looking for is to take out a window from the cyclic
ordering (or force it *not* to be the least recently used).  I believe
that the buffer list is not relevant to this problem; the way I
understand it, the buffer list is orthogonal with the window ordering
and only the window ordering decides which window is going to be
associated with a new buffer.

So far, the only hack I thought of is to add a find-file-hook that
would select, in turn, all the windows I want to keep visible just
before reading a file.  This wouldn't work when a buffer is simply
popped (made visible).

To put things in perspective, I'm thinking of writing a mouse
interface to the existing gdb mode.  I know that an xgdb exists, but
apparently it is not very compatible with the latest X11 and a newer
version is not promised for *at least* 6 months.  My idea is to build
something similar to dbxtool (that's what the people here want) on top
of the emacs-gdb interface.  To do this, I need to keep three windows
from disappearing: the command window, the display window, and the
"buttons" window.

UniPress emacs (starting with version 2.15, I believe) had something
called "freeze-window" that would make it immune to changes in other
windows.  This is the sort of thing I'm looking for.

I haven't found anything in the elisp manual.  Any guru out there to
give me a hint, a place to start?  I'm willing to write elisp and C if
necessary.

Thanks,

-- 
Martin Boyer                            mboyer@ireq-robot.hydro.qc.ca
Institut de recherche d'Hydro-Quebec    mboyer@ireq-robot.uucp
Varennes, QC, Canada   J3X 1S1
+1 514 652-8412