From: Alex Schroeder <alex@emacswiki.org>
Subject: gnus in one window...
Date: Mon, 02 Dec 2002 22:54:43 +0100 [thread overview]
Message-ID: <87smxghysc.fsf@emacswiki.org> (raw)
I am trying to run Gnus in one window only... Until now, I have
always used a separate Gnus frame, but now I decided to try for myself
wether it is possible and wether I would like it or not.
So I started out with this:
(setq gnus-use-full-window nil)
(gnus-add-configuration '(article (article 1.0 point)))
(gnus-add-configuration '(summary (summary 1.0 point)))
(gnus-add-configuration '(group (group 1.0 point)))
(gnus-add-configuration '(message (message 1.0 point)))
(gnus-add-configuration '(reply (message 1.0 point)))
(gnus-add-configuration '(reply-yank (message 1.0 point)))
(gnus-add-configuration '(forward (message 1.0 point)))
(gnus-add-configuration '(mail-bounce (message 1.0 point)))
One point where this confuses Gnus is when reading an article opens
another extra window -- such as when BBDB recognizes the author. To
test, split windows, switch one of them to the Group buffer. Enter a
group. In the summary, select a posting by an author stored in the
BBDB. The Gnus window is now split again, with one of the windows
showing the BBDB. Now use s to return to the summary. The BBDB
window remains visible. Now select a posting by an author not in the
BBDB. The article buffer will now cover the entire frame.
Similar things happen when a BBDB pops up when I view an article, then
use s to move to the summary, and q to return to the group buffer --
the window configuration is messed up with the group window occuping
all the space that is not used by the BBDB window.
Strange.
Has anybody else played around with this? Any ideas of where to start
looking? Right now I feel like preventing the BBDB buffer from ever
popping up. Perhaps that helps... :)
Alex.
next reply other threads:[~2002-12-02 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 21:54 Alex Schroeder [this message]
2002-12-28 18:40 ` Lars Magne Ingebrigtsen
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=87smxghysc.fsf@emacswiki.org \
--to=alex@emacswiki.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).