bug#57848: 29.0.50; Problems with private tab-line-tab-name-function

[Juri Linkov]

>> This is because of how window-prev-buffers behaves.  We could fix this
>> behavior to not change the order of the existing window-prev-buffers
>> after selecting a buffer that already exists in window-prev-buffers,
>> or at least to add an option to do so.
>
> Hmm - sounds quite drastic.  Not sure I would want that changed behavior
> when I don't use tabs.  Conceptually I would prefer that the tab order
> would not depend on such low-level things, things that much more user
> visible stuff depends on.

I tried to implement the window-local tab-line by using a window-parameter.
But the immediate drawback was that the keys 'C-x <left>' (previous-buffer)
and 'C-x <right>' (next-buffer) can't be used anymore to go to the
previous/next tab that is the same as the buffer in the window-buffers list.