From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Why no multiple *Article* buffers?
Date: 20 May 1996 19:44:42 +0200 [thread overview]
Message-ID: <x6689r6xyt.fsf@eyesore.no> (raw)
In-Reply-To: Scott Blachowicz's message of Mon, 20 May 1996 08:33:20 -0700
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.
--
"Yes. The journey through the human heart
would have to wait until some other time."
next prev parent reply other threads:[~1996-05-20 17:44 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 [this message]
1996-05-21 0:46 ` Colin Rafferty
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=x6689r6xyt.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/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).