Gnus development mailing list
 help / color / mirror / Atom feed
From: craffert@ml.com (Colin Rafferty)
Subject: Re: Why no multiple *Article* buffers?
Date: 20 May 1996 20:46:33 -0400	[thread overview]
Message-ID: <ocrzq72q2dy.fsf@spssunp.spspme.ml.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 20 May 1996 19:44:42 +0200

Lars Magne Ingebrigtsen writes:
> Scott Blachowicz <scott@statsci.com> writes:

>> So, what possible use is it to have a single *Article* buffer to handle
>> multiple *Summary* buffers? 

> Having multiple article buffers can be somewhat confusing.  At least I
> thought so after I switched to multiple article buffers, which can be
> done by setting `gnus-single-article-buffer' to nil.

Agree with Scott, respectfully disagree with Lars.  As one of the major
testers of multiple article buffers, I can tell you that they make life
wonderful.  That is, if you are using multiple frames.  But if you are
not using multiple frames, you are not using Gnus to its full potential.

I have one virtual window in vtwm in which I do all mail/news reading.
The left half of the screen has a stack of emacs frames, each of which
holds a single summary/article pair of buffers for one group.

M-C-F9 lowers the current frame so that I can cycle through groups.
With all this, each Gnu frame has a matching *Summary* and *Article*,
and when I cycle frames, I see the actual articles.  A single *Article*
buffer would hopelessly confuse everything.

What I should really do is have `gnus-select-group-hook' change the
frame out from under Gnus, and have `gnus-summary-exit-hook' kill the
frame.  This would make life very cool (or very confusing).

-- 
Colin Rafferty

"The technophiles are taking us all on an utterly     |   "Whee!"
 reckless ride into the unknown."  -- Unabomber       |     -- Me


      reply	other threads:[~1996-05-21  0:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-20 15:33 Scott Blachowicz
1996-05-20 17:44 ` Lars Magne Ingebrigtsen
1996-05-21  0:46   ` Colin Rafferty [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=ocrzq72q2dy.fsf@spssunp.spspme.ml.com \
    --to=craffert@ml.com \
    /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).