Re: MY window tree!

["Juanma Barranquero" <lekktu@gmail.com>]

On 1/15/07, Lennart Borgman (gmail) <lennart.borgman@gmail.com> wrote:

> But overlays are bound to buffers AFAIK. I can not see there are any
> problems with buffers here. Or am I missing something?

Buffer B's mode, A-mode, has functions to create and maintain a list
of overlays, O1..ON, some of which have a 'window property. You change
windows and copy a subset of O1..ON, O'M..O'K. Now the buffer has
overlays A-mode knows nothing about. If A-mode has, for example, a
command to move some subset of O1..ON, it will leave behind O'M..O'K
even if they're copies of some of the ones moved.

The problem is that by creating new overlays you're bypassing A-mode's
expectations about what B contains. If B detects the overlays by
searching them, fine. But B can use shortcuts like lists, or perhaps
hash tables.

> Is not the only binding from overlays to windows the 'window property
> that can be set for some overlays.

Perhaps, but I'm talking of the binding from overlays to buffers to
mode functions that manipulate them.

> but it would be good to
> have primitives for handling cases like this there.

Agreed. (After The Release And Other Usual Disclaimers)

                    /L/e/k/t/u