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

[Michael Heerdegen]

Juri Linkov <juri@linkov.net> writes:

> 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.

Michael.