From: Steve Dunham <dunham@dunham.tcimet.net>
Subject: Re: Problem with nnvirtual in 0.72?
Date: 09 Dec 1996 21:37:23 -0500 [thread overview]
Message-ID: <m24thvi0po.fsf@dunham.tcimet.net> (raw)
In-Reply-To: Matt Pharr's message of 04 Dec 1996 17:22:58 -0800
Matt Pharr <mmp@graphics.stanford.edu> writes:
> David Moore <dmoore@UCSD.EDU> writes:
> > Jason L Tibbitts III <tibbs@hpc.uh.edu> writes:
> > > Unfortunately after I upgraded to 0.72 I found that after reading all of
> > >the articles in the group and calling gnus-group-get-new-news the unread
> > >article count would be some large number (like 1300, I assume the sum of
> > >(max - min article) for each group). It seems that it's losing the list
> > >of read articles, even though a long list shows up in the group info.
> > ..
> > > Has anyone seen this? I'm not submitting this as a bug report because I
> > >could be screwing something up and since I don't really know where to
> > >start
> > > looking it would be a pretty pitiful bug report.
> Another little piece of data about this: I raised the level of the groups
> that make up one of my virtual groups to 3 and started newsreading. When I
> started gnus, all was fine--there were a handful of new messages. After I
> read news in one of the virtual groups with new news and caught up, exited
> and returned to the Group buffer, all of the groups that made up the
> virutal group has a jazillion unread messages in them. So maybe it's a
> problem with how nnvirtual handles catching up...
This problem is still there in 0.74... I have one nnvirtual group made
up of two level 6 (unsubscribed) groups. Whenever I catch up in the
nnvirtual group, it screws up the the read messages count in the
constituent groups. i.e.,
U 6207: comp.os.linux.development.apps
U 1353: comp.os.linux.development.system
4610: nnvirtual:comp.os.linux.development
("comp.os.linux.development.apps" 6
((1 . 23143))
((reply 28332 28811)))
I change it to:
("comp.os.linux.development.apps" 6
((1 . 28811))
((reply 28332 28811)))
(and save with C-c C-c)
then do M-g on the virtual group and get:
U 539: comp.os.linux.development.apps
U 1353: comp.os.linux.development.system
1768: nnvirtual:comp.os.linux.development
Then enter the virtual group and do a "c y" and we are back to
U 6207: comp.os.linux.development.apps
U 1353: comp.os.linux.development.system
4613: nnvirtual:comp.os.linux.development
"G E" on the apps group gives:
("comp.os.linux.development.apps" 6
((1 . 23143))
((reply 28332 28811)))
Funny thing is, "c y" in the *Groups* buffer seems to work right...
Steve
dunham@gdl.msu.edu
next prev parent reply other threads:[~1996-12-10 2:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-12-02 22:48 Jason L Tibbitts III
1996-12-03 6:00 ` David Moore
1996-12-03 7:15 ` Matt Pharr
1996-12-03 19:14 ` Han Pilmeyer
1996-12-05 1:22 ` Matt Pharr
1996-12-10 2:37 ` Steve Dunham [this message]
1996-12-03 2:24 St. Suika Fenderson Roberts
1996-12-03 3:55 ` Jason L Tibbitts III
1996-12-03 5:24 ` Han Pilmeyer
1996-12-10 18:46 St. Suika Fenderson Roberts
1996-12-10 22:47 ` David Moore
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=m24thvi0po.fsf@dunham.tcimet.net \
--to=dunham@dunham.tcimet.net \
/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).