Re: window-next-buffers

[martin rudalics]

> Then we need just one list of buffers (visited in the window)
> and the pointer referencing the currently displayed buffer
> (or a numeric index of the position of the currently displayed
> buffer in the list of visited buffers).

A window's previous buffers are perused as follows:

(1) For navigating the buffers shown in a window.  This calls
    `switch-to-prev-buffer' with BURY-OR-KILL nil and preferably does
    not show a buffer from the window's next buffers.

(2) For burying or killing the buffer shown in a window.  This may call
    `switch-to-prev-buffer' with BURY-OR-KILL non-nil and can show a
    buffer from window's next buffers.

(3) For quitting a window.  This works on the window's previous buffers
    directly and can show a buffer from window's next buffers.

So any optimization for (1) must make sure that operations (2) and (3)
are not harmed.  In addition you will have to do the proper action for
`set-window-buffer'.

And the most annoying problem, namely that a buffer on one of these
lists gets killed while I can't access these lists because they are
hidden by a window excursion, must be handled too (maybe directly in
`set-window-configuration').

martin