From: Steve Baumgarten <sbb@panix.com>
Subject: Re: nnvirtual not working with September 0.51 / XEmacs 19.14b14
Date: Tue, 12 Mar 1996 08:51:30 -0500 (EST) [thread overview]
Message-ID: <199603121351.IAA17566@panix3.panix.com> (raw)
In-Reply-To: <m2n35mbx2h.fsf@deanna.miranova.com>
Steven L. Baur writes:
Michael> First of all, fetching the article headers takes *forever*, usually
Michael> (with more than 20 articles) on the order of several minutes.
I've found this to be sort of an on-again off-again sort of thing. A
versions back nnvirtual was working as smoothly as it ever had. Now
it takes forever (>15 minutes) to load the nnvirtual group I have, no
matter what the unread article counts are in the component groups. I
have successfully loaded nnvirtual groups of up to around 2000
articles in the past.
I should have reported this some time ago, but I guess now is better
than never. I, too, have had similar problems, with an nnvirtual
group that worked smoothly in Gnus 5.0.13 and I believe in earlier
versions of sgnus; now, however, I've had to delete it because of
incredibly lengthy "Checking new news..." times. (The group in
question had about a half-dozen newsgroups in it; the underlying
groups had some ticked and/or cached articles and often have several
cross-postings.)
Here is a list of what else doesn't appear to work:
M-g is broken. With previous behavior, one could read one of the
nnvirtual component groups, then move the cursor to the nnvirtual
group and hit M-g and the article count would be reduced by the number
of articles read in the component group. This is not true now.
Agreed. I've seen exactly this behavior.
Sorry I wasn't able to track this down more precisely, or report it
sooner...
Steve Baumgarten
sbb@panix.com
prev parent reply other threads:[~1996-03-12 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-11 13:27 Michael Sperber [Mr. Preprocessor]
1996-03-12 7:16 ` Steven L Baur
1996-03-12 13:51 ` Steve Baumgarten [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=199603121351.IAA17566@panix3.panix.com \
--to=sbb@panix.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).