Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Gnus lies about downloaded state
Date: Sun, 19 Jan 2003 10:42:53 -0600	[thread overview]
Message-ID: <uwul1w0oi.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <844r867ekk.fsf@lucy.is.informatik.uni-duisburg.de>

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> I'm afraid I kinda lost track about the situation now.  I still see
> problems with the indication of the downloaded state, but I have more
> data.  In this group, I have some ticked (and thus, cached) articles,
> and there are some old articles that I have marked as unread with
> M-u.  And finally, there are unseen articles (marked with ".").  They
> are marked as downloaded because I did `J s' after `g'.
>
> In this case, the M-u'd articles are marked as not downloaded.
> Now I read the new message and then hit M-g in the group.
> Then the M-u'd messages are correctly marked as downloaded: I see
> the + for %O and the color is the default color.
>
> I get the feeling that this is not about corruption of the state that
> the agent keeps.  Instead, it seems that the summary buffer display
> interprets the data wrongly.  But it is somewhat strange that the
> presence of "." (unseen?) articles has effect on that interpretation.
>
> FWIW, ticked (and thus, cached) articles are also always shown in the
> "undownloaded" face and with %O=-.


OK, have you applied my patch to gnus-sum?  That patch will not fix
the face being displayed.  However, it WILL fix a major problem with
updating the downloaded mark.  I'm reluctant to check-in this patch
because it is in such a basic function.  My concern is that other
routines may actually depend on the bug's existance :(.

Kevin



  reply	other threads:[~2003-01-19 16:42 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
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 [this message]
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=uwul1w0oi.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).