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

[Juri Linkov]

close 57848 29.0.50
thanks

>> Very cool, thanks.  I'll try it out a bit and report back.
>
> Ok - works perfectly so far!  I think I'm happy with this change.

Thanks for helping to fix the %-construct bug, and to improve
caching functions.  So I'm closing this bug report.

> I have a related question, though: When browsing Info, how would you
> configure things so that the tabs in the tab line are ordered similar to
> what you get in an Internet browser: new tabs are opened at the
> rightmost position (or next to the current tab), and the tabs are
> otherwise not sorted automatically in any way.  Can this currently be
> achieved?  It seems that there is always some unavoidable hard-coded
> sorting happening.

By default new tabs are opened at the rightmost position because
this is what happens with window-next-buffers/window-prev-buffers.
So the order is not changed as long as you use `C-x <left>'
(previous-buffer) and `C-x <right>' (next-buffer) to navigate
tab buffers.  However, switching to a buffer moves it to the end
of the tab-line corresponding to window-prev-buffers.
If you want, you could create a new tab-line-tabs-function
based on tab-line-tabs-window-buffers, that will sort
window-buffers using their creation order preserved in
some new window-local variable.