GNU bug report logs -
#29696
Reading summary keys from article changes window configuration
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#29696: Reading summary keys from article changes window configuration
which was filed against the emacs,gnus package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 29696 <at> debbugs.gnu.org.
--
29696: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29696
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
On Wed, 13 Dec 2017 20:24:43 +0000, Basil L. Contovounesios wrote:
> Using Gnus with the user option pop-up-frames set to 'graphic-only, I
> observe the following behaviour:
> 1. Visit an article.
> 2. Make article window the sole window in its containing frame.
> 3. Type = (gnus-summary-expand-window).
> Expected result: The article's summary replaces the article in the
> frame's sole window.
> Actual result: The expected result plus an additional frame displaying
> the corresponding summary buffer. In other words, expanding the article
> window causes an extraneous frame to be created.
Confirmed and applied your patch in the emacs-26 branch. Thanks.
> I believe this is caused by a call to pop-to-buffer within
> save-window-excursion in the function gnus-article-read-summary-keys.
> Is the call to pop-to-buffer really necessary for the purpose of key
> lookup? Wouldn't changing the current buffer suffice, so as not to
> affect the window configuration in the first place?
I agree, only changing the buffer is sufficient in that case.
I don't know why pop-to-buffer is used, but it seems to be there
from the beginning (it is as is in Red Gnus 0.01 of 1996).
I guess it was beyond imagination that pop-to-buffer may raise
a new frame when there is no frame visiting the buffer, and why
this wasn't discovered so far is that those who set pop-up-frames
to nin-nil normally are not so many.
> If so, please consider the attached patch which addresses this. The
> docstring of save-window-excursion even warns of the possibility of
> behaviour like the one I describe.
> The information gathered by gnus-bug follows my signature.
> Thanks,
[Message part 3 (message/rfc822, inline)]
[0001-Do-not-pop-to-buffer-for-reading-gnus-summary-keys.patch (text/x-diff, attachment)]
[Message part 5 (text/plain, inline)]
Using Gnus with the user option pop-up-frames set to 'graphic-only, I
observe the following behaviour:
1. Visit an article.
2. Make article window the sole window in its containing frame.
3. Type = (gnus-summary-expand-window).
Expected result: The article's summary replaces the article in the
frame's sole window.
Actual result: The expected result plus an additional frame displaying
the corresponding summary buffer. In other words, expanding the article
window causes an extraneous frame to be created.
I believe this is caused by a call to pop-to-buffer within
save-window-excursion in the function gnus-article-read-summary-keys.
Is the call to pop-to-buffer really necessary for the purpose of key
lookup? Wouldn't changing the current buffer suffice, so as not to
affect the window configuration in the first place?
If so, please consider the attached patch which addresses this. The
docstring of save-window-excursion even warns of the possibility of
behaviour like the one I describe.
The information gathered by gnus-bug follows my signature.
Thanks,
--
Basil
Gnus v5.13
GNU Emacs 27.0.50 (build 9, x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2017-12-05
This bug report was last modified 7 years and 220 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.