Gnus development mailing list
 help / color / mirror / Atom feed
From: David Moore <dmoore@UCSD.EDU>
Subject: Re: Problem with nnvirtual in 0.72?
Date: 02 Dec 1996 22:00:28 -0800	[thread overview]
Message-ID: <rv7mn0dv5v.fsf@sdnp5.ucsd.edu> (raw)
In-Reply-To: Jason L Tibbitts III's message of 02 Dec 1996 16:48:54 -0600

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.

	I haven't seen it yet.  If you weren't seeing the problem in
0.70, maybe it's related to the other mysterious group count bug.
Although, you know, I do seem to vaguely recall all something like what
you just described happening to me recently.  ie, the group info seemed
correct but the display was for the whole group.  Maybe it was on an
nndir of the gnus-bugs archive, when ange-ftp got flakey?  Hah, that's
even worse bug report. :)

	Questions:
1) Do you read the component groups seperately from the virtual group?
2) If so, do you have nnvirtual-always-rescan set to t?
3) Do you have the component groups before, after, or both to the
virtual group in the *Group* buffer.



-- 
David Moore <dmoore@ucsd.edu>       | Computer Systems Lab      __o
UCSD Dept. Computer Science - 0114  | Work: (619) 534-8604    _ \<,_
La Jolla, CA 92093-0114             | Fax:  (619) 534-1445   (_)/ (_)
<URL:http://oj.egbt.org/dmoore/>    | Solo Furnace Creek 508 -- 1996!


  reply	other threads:[~1996-12-03  6:00 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 [this message]
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
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=rv7mn0dv5v.fsf@sdnp5.ucsd.edu \
    --to=dmoore@ucsd.edu \
    /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).