From: Scott Blachowicz <scott@statsci.com>
Subject: Why no multiple *Article* buffers?
Date: Mon, 20 May 1996 08:33:20 -0700 [thread overview]
Message-ID: <m0uLWxU-000r3uC@main.statsci.com> (raw)
Hi-
As I was sitting here hitting `g' to get me an article and wondering why I
wasn't seeing anything, I remembered some discussion a while back talking
about multiple *Article* buffers and how they didn't exist. I did some
poking around and found that I had managed to leave iconified a frame with
a different *Summary* buffer and *Article* buffer in it.
So, what possible use is it to have a single *Article* buffer to handle
multiple *Summary* buffers? Or, rather, if my configuration is setup to
have *Summary* and *Article* buffers in the same frame, why shouldn't I
get multiple *Article* buffers if I can get multiple *Summary* buffers?
--
Scott Blachowicz Ph: 206/283-8802x240 Mathsoft (Data Analysis Products Div)
1700 Westlake Ave N #500
scott@statsci.com Seattle, WA USA 98109
Scott.Blachowicz@seaslug.org
next reply other threads:[~1996-05-20 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-20 15:33 Scott Blachowicz [this message]
1996-05-20 17:44 ` Lars Magne Ingebrigtsen
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=m0uLWxU-000r3uC@main.statsci.com \
--to=scott@statsci.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).