bug#69993: Wrap window buffers while cycling

[martin rudalics]

>> But then we would have to handle any call of set_window_buffer that
>> replaces a window's buffer with one that has been previously shown in
>> that window.
>
> Indeed, this is why I asked to add a new hook after set-window-buffer,
> like the hook record-window-buffer is called before set-window-buffer.

Are you sure that 'window-buffer-change-functions' can't catch this
already?  IIUC all you need is to to know whether the current buffer of
a window does not equal the value returned by 'window-old-buffer' for
that window.

martin