bug#38354: 27.0.50; Implement display action display-buffer-in-tab

[Juri Linkov <juri@linkov.net>]

>> I have no preference, but don't understand why the implementation
>> should provide only one way, but not another.  Is it what users expect?
>
> IIRC that's how we interpreted the term "reuse" in the past - do not
> change configurations if we can avoid it.  But I have no preference
> either.

Still unclear what window currently code prefers in case of two
or more windows displaying the same buffer, or when the buffer
is displayed in windows of two or more frames.  What window/frame it
reuses?  Just the first found?  Is it possible to express such
preferences for multiple windows/frames in display-buffer-alist?

>> It should close the tab only on quitting the window with the buffer
>> whose displaying created the tab.  For example, when
>> 'switch-to-buffer-other-tab' creates a new tab, then quitting
>> its buffer should close the tab.
>>
>> This is the same logic as for creating/deleting the window, e.g.
>> 'C-h f car RET' creates a window, but typing 'q' in Help buffer
>> deletes the window.  'q' in a new tab should close it as well.
>
> OK.  But what if another action adds something to such a tab and we
> then quit the window.  Or is such a scenario impossible?

Does a similar situation happen in case of window quitting?
Then the same logic could be reused for tab quitting.
When another buffer is displayed in the same window,
then quit-window doesn't delete the window with another buffer?