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

Previous Next

Package: emacs;

Reported by: Al Haji-Ali <abdo.haji.ali <at> gmail.com>

Date: Thu, 6 Jun 2024 00:11:02 UTC

Severity: wishlist

Found in version 29.1

Fixed in version 31.0.50

Done: Juri Linkov <juri <at> linkov.net>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

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: bug#71386: 29.1; Frame is auto-deleted even when it has multiple tabs
Date: Sun, 30 Mar 2025 21:37:40 -0400
[Message part 1 (text/plain, inline)]
On Sun, Mar 30, 2025 at 10:38 AM Ship Mints <shipmints <at> gmail.com> wrote:

> 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.
>

Hi, Juri,

[The patch probably needs to be rebased on master but I was able to apply
it by hand, I think.]

The conditions it's testing for are not ones that exist in my case.

The conditions are:

I'm not using the display actions in my configuration and I don't invoke
the tab-bar functions that use it.

I have two tabs on a newly opened frame.  Both tabs have only one window.
If I'm on tab 2, and I eval (kill-buffer), the frame disappears.

From inside window-deletable-p: tab-bar-mode=t #tabs=2 quit-restore
parameter=nil window-dedicated-p=nil frame-root-window=t

HTH (hope that helps and happy to help),

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

This bug report was last modified 34 days ago.

Previous Next


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