Re: [patch] two patchs about tab-bar.el

[Juri Linkov <juri@linkov.net>]

> I have two tabs:
>
> 1. *scratch*  2. *scratch*, *Messages*
>
> and current-tab is 2
>
> if I switch-to-buffer *scratch*, it will switch to tab 1, instead of
> jump to window '*scratch*' in current tab.
>
> for current-tab is not at the beginning of tabs.

Please send your customized settings related to tab-bar.
I see that you set 'tab-bar-tab-name-function' to 'tab-bar-tab-name-all'.
What other tab-bar customization do you have that causes buffer-switching
also select another tab?  Is it something in display-buffer-alist
that is customized to use display-buffer-in-tab?

>>>  If ALIST contains a `reusable-frames' entry, its value determines
>>>  which frames to search for a reusable tab:
>>> -  nil -- the selected frame (actually the last non-minibuffer frame)
>>> +  nil -- do not reuse any frames.
>>>    A frame   -- just that frame
>>>    `visible' -- all visible frames
>>>    0   -- all frames on the current terminal
>>>    t   -- all frames.
>>> +  others -- selected frame.
>>
>> I wonder where did you get the value 'others' that means the selected frame?
>
> (defun tab-bar--reusable-frames (all-frames)
>   (cond
>    ((eq all-frames t) (frame-list))
>    ((eq all-frames 'visible) (visible-frame-list))
>    ((framep all-frames) (list all-frames))
>    (t (list (selected-frame)))))

Thanks, I thought that `others' is a symbol because is looks like `visible'.
If you meant that all other values affect the selected frame, then better
to use such wording: "other non-nil values".