Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Gnus lies about downloaded state
Date: Wed, 15 Jan 2003 00:08:21 -0600	[thread overview]
Message-ID: <uk7h79c8a.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <uy95n9xxy.fsf@adobe.com>

Danny Siu <dsiu@adobe.com> writes:

> i am seeing the same thing.  i just did 'J s' and am sure all articles are
> downloaded but the summary buffer still highlights those as undownloaded.
>
> it didn't happen yesterday.  i am using the latest from cvs.
>
> screen shot attached.
>
> Kai Großjohann writes:
>
>   Kai> Look at this screenshot.  The "-" in the leftmost column means the
>   Kai> article isn't downloaded, but Gnus is unplugged, and I can see the
>   Kai> message!
>
>   Kai> What's the story?
>
>   Kai> I think this happened only recently.  -- Ambibibentists unite!
>

OK OK.  I can be hard headed at times but this isn't one of them.

I believe that I found this myself just the other night.  In any case,
I've been unable to reproduce this problem with the 6.131 version of
gnus-agent. Pls download it then repeat your tests.

VERY IMPORTANT: 
Run gnus-agent-regenerate to repair your groups first!!  You've
already downloaded a number of articles, no need to download them
again.

Here's what I tried.
1) Opened gnus.ding
2) Set the downloadable mark on 100 articles (A random mix of headers
   with about 70 already having their article's fetched into the
   agent).
3) Closed gnus.ding
4) Executed fetch session ('J s') in the group buffer.
5) Opened gnus.ding; At this point, all of the downloadable marks were
   gone and all articles displayed with a downloaded(+) mark.

Kevin



  reply	other threads:[~2003-01-15  6:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14 17:28 Kai Großjohann
2003-01-14 21:42 ` kgreiner
2003-01-15  7:11   ` Kai Großjohann
2003-01-15  7:12   ` Kai Großjohann
2003-01-15  7:16   ` Kai Großjohann
2003-01-14 22:19 ` Danny Siu
2003-01-15  6:08   ` Kevin Greiner [this message]
2003-01-15  8:56     ` Danny Siu
2003-01-15 14:16     ` Kai Großjohann
2003-01-15 15:12       ` Kevin Greiner
2003-01-15 16:07         ` Kai Großjohann
2003-01-15 21:07           ` Kevin Greiner
2003-01-16  4:29           ` Kevin Greiner
2003-01-16  7:52             ` Danny Siu
2003-01-16 13:02               ` Kevin Greiner
2003-01-16 20:53                 ` Danny Siu
2003-01-16 22:31                   ` Kevin Greiner
2003-01-16 23:08                     ` Danny Siu
2003-01-17  3:35                       ` Kevin Greiner
2003-01-18 13:49             ` Kai Großjohann
2003-01-19 16:42               ` Kevin Greiner
2003-01-22 19:38                 ` Danny Siu
2003-01-23  4:10                   ` Kevin Greiner
2003-01-23 10:39                     ` Kai Großjohann
2003-01-23 13:16                       ` Kevin Greiner
2003-01-23 14:11                         ` Kai Großjohann
2003-01-23 19:45                     ` Danny Siu
2003-01-23 10:30                   ` Kai Großjohann
2003-01-15 18:27         ` Danny Siu
2003-01-16  1:21 Danny Siu

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=uk7h79c8a.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.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).