From: David Z Maze <dmaze@mit.edu>
Subject: Re: Wider summary buffer while browsing articles
Date: Thu, 21 Aug 2003 14:44:28 -0400 [thread overview]
Message-ID: <87isoqam0j.fsf@everett.mit.edu> (raw)
In-Reply-To: <87he4bvsyz.fsf@plato.moon.paoloamoroso.it>
Paolo Amoroso <amoroso@mclink.it> writes:
> When accesing a group, the summary buffer takes all the space
> available in the Gnus window. After reading an article, it shrinks
> considerably to leave room for the text. When the user is done with
> the article, and browses the summary buffer for another interesting
> article, the summary buffer window is still small.
>
> Is it possible to temporarily enlarge the summary buffer to the full
> size of the Gnus window?
Press '=' from either the summary or article buffer. (Or use the
normal Emacs C-x 1 or C-x 0 commands.)
--
David Maze dmaze@mit.edu http://www.mit.edu/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
next parent reply other threads:[~2003-08-21 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87he4bvsyz.fsf@plato.moon.paoloamoroso.it>
2003-08-21 18:44 ` David Z Maze [this message]
[not found] ` <873cfunb4q.fsf@enberg.org>
2003-08-21 19:28 ` Paolo Amoroso
[not found] ` <87ada1c1i4.fsf@plato.moon.paoloamoroso.it>
2003-08-23 6:53 ` Ivan Boldyrev
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=87isoqam0j.fsf@everett.mit.edu \
--to=dmaze@mit.edu \
/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).