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

Previous Next

Full log

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

From: Juri Linkov <juri <at> linkov.net>
To: martin rudalics <rudalics <at> gmx.at>
Cc: Eli Zaretskii <eliz <at> gnu.org>, abdo.haji.ali <at> gmail.com,
 Ship Mints <shipmints <at> gmail.com>, 71386 <at> debbugs.gnu.org
Subject: Re: bug#71386: 29.1; Frame is auto-deleted even when it has
 multiple tabs
Date: Thu, 03 Apr 2025 09:55:17 +0300

>> Martin, could you help to understand why this line fails
>>
>>        ;; FIXME: uncomment (should (equal (buffer-name) "*Messages*"))
>>
>> in 'tab-bar-tests-quit-restore-window' in test/lisp/tab-bar-tests.el?
>>
>> It selects an unexpected buffer.  Maybe because the frame focus
>> is broken?
>
> IIUC the context is
>
>       (quit-window)
>       (should (eq (length (window-list)) 1))
>       (should (eq (length (frame-list)) 2))
>       ;; FIXME: uncomment (should (equal (buffer-name) "*Messages*"))
>
> What is 'quit-window' supposed to do - delete the frame?

'q' is supposed to delete one of two windows and move focus
to the remaining window:

1. C-x 5 5 C-h i
2. C-h e
3. q

should make the selected window with the buffer *Messages*.
And it does when trying the same interactively.

> In either case we would have to know which window gets selected when
> the 'quit-window' call returns and which buffer it shows.

Interactively it selects the *Messages* window, but not in tests.
This is because for tests window-system is nil, so it behaves
weirdly in noninteractive tests.

Previous Next

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