From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: summary window width
Date: Sun, 05 Sep 2010 21:09:01 +0800 [thread overview]
Message-ID: <87eid8cp76.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m3bp8c2wtn.fsf@quimbies.gnus.org>
On Sun, Sep 05 2010, Lars Magne Ingebrigtsen wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> I have a pair of particularly wide monitors, and generally find that
>> splitting frames vertically is a good use of space. If the gnus group
>> buffer is on the left, say, and I enter a group, the resulting summary
>> buffer munches my whole frame. Is there a simple way to keep that from
>> happening?
>
> No, I don't think so, but you can have the group buffer on the left and
> the summary buffer on the right, and so on. See the "Window Layout"
> section in the manual.
No no, that was exactly right! Initial experiments indicate I'll
definitely be able to get it to work the way I want it, I just needed to
be pointed towards the "Window Layout" section. Thanks a lot!
E
prev parent reply other threads:[~2010-09-05 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 12:19 Eric Abrahamsen
2010-09-05 12:34 ` Lars Magne Ingebrigtsen
2010-09-05 13:09 ` Eric Abrahamsen [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=87eid8cp76.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.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).