bug#59862: quit-restore per window buffer

[Juri Linkov <juri@linkov.net>]

>> I suppose it will affect only interactive uses of 'kill-buffer'.
>
> Why?  It affects all uses of 'kill-buffer'.

I'm not sure about this, I just had a feeling that killing
a temporary buffer should not affect its window.  But
a test case is needed to see if this is a real problem.

>> PS: I noticed one difference between handling of frames and tabs:
>>
>> C-x 5 5   ;; other-frame-prefix
>> C-h i     ;; info
>> C-h e     ;; view-echo-area-messages
>> q         ;; quit-window
>> This deletes the Info window, and doesn't delete the frame.
>> Everything is correct.
>>
>> C-x t t   ;; other-tab-prefix
>> C-h i     ;; info
>> C-h e     ;; view-echo-area-messages
>> q         ;; quit-window
>> This doesn't close the tab (correct),
>> but doesn't delete the Info window.
>> This differs from the frame case that keeps
>> only the Messages window on the frame.
>
> Suppose you do
>
> C-h i     ;; info
> C-h e     ;; view-echo-area-messages
> q         ;; quit-window
>
> Then the difference is obvious.  The C-h i reuses the one existing
> window showing *scratch*.  'display-buffer-record-window' cannot tell
> this case apart from the one where a user does want to show *scratch*
> again in that window after being done with *info*.

But there is no *scratch* in the list of previous buffers for 'C-x t t C-h i'
(that can be confirmed when tab-line is enabled), so the user won't expect
to show *scratch*.  And indeed the frame case doesn't show *scratch*.
I hoped that it would be possible for the tab case to do the same,
but I don't know how the frame case is handled to do the right thing.