Re: window-next-buffers

[Juri Linkov]

>> This sounds like an overly optimization.  But actually I can't find
>> a case where `next-buffer' would fail to get information about markers.
>> Is this because information about markers of next buffers is retrieved
>> from `window-prev-buffers'?
>
> Yes.  In `switch-to-next-buffer'
>
> (assq buffer (window-prev-buffers window))
>
> provides this information.  `window-next-buffers' is exclusively used
> for buffer navigation within a window.  `window-prev-buffers' is used in
> other occasions like `quit-window' where I don't care about a window's
> next buffers.

IIUC this means that a set of next-buffers is a subset of prev-buffers.

>> Isn't better to push a new window to the top of the list of next buffers
>> to not lose information about the rest of next buffers?
>
> Can you elaborate what you mean here?  A new window has neither previous
> nor next buffers.

Sorry, I meant "a new buffer" (displayed in the selected window
by `set-window-buffer').