GNU bug report logs - #71386
29.1; Frame is auto-deleted even when it has multiple tabs

Previous Next

Full log

Message #166 received at 71386 <at> debbugs.gnu.org (full text, mbox):

From: Ship Mints <shipmints <at> gmail.com>
To: martin rudalics <rudalics <at> gmx.at>
Cc: Eli Zaretskii <eliz <at> gnu.org>, abdo.haji.ali <at> gmail.com,
 71386 <at> debbugs.gnu.org, Juri Linkov <juri <at> linkov.net>
Subject: Re: bug#71386: 29.1;
 Frame is auto-deleted even when it has multiple tabs
Date: Sun, 30 Mar 2025 10:38:48 -0400

[Message part 1 (text/plain, inline)]

On Sun, Mar 30, 2025 at 9:55 AM martin rudalics <rudalics <at> gmx.at> wrote:

>  > I'll give it a try.  I have a question, though, and sorry if the answer
> is
>  > obvious.  Where is the window parameter 'quit-restore get set 'tab to
> begin
>  > with?
>
> At the very end of 'display-buffer-record-window'
>
>     ((eq type 'tab)
>      ;; WINDOW has been created on a new tab.
>      (set-window-parameter
>       window 'quit-restore
>       (list 'tab 'tab (selected-window) buffer)))))
>
> I suppose.  The initial call is from 'display-buffer-in-new-tab'.
>

Makes sense.  Thank you.  I don't use those display actions.  Juri's patch
should address the main issue for both use cases.  I hope to try it out
later today.

Minor point...when reading through the code, I think the docstrings for
'window--display-buffer' and 'display-buffer-record-window' need to add
'tab to the TYPE section in each.

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.