From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Basil L. Contovounesios <contovob@tcd.ie>
Cc: 29696-done@debbugs.gnu.org
Subject: bug#29696: Reading summary keys from article changes window configuration
Date: Thu, 14 Dec 2017 13:45:57 +0900 [thread overview]
Message-ID: <b4md13h3oje.fsf@jpl.org> (raw)
In-Reply-To: <87lgi6pe9g.fsf@gmail.com>
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,
prev parent reply other threads:[~2017-12-14 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 20:24 bug#29696: Reading summary keys from article changes window configuration Basil L. Contovounesios
2017-12-14 4:45 ` Katsumi Yamaoka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4md13h3oje.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=29696-done@debbugs.gnu.org \
--cc=contovob@tcd.ie \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.