Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: problems with gnus-newsgroup-unseen and gnus-newsgroup-data
Date: 17 May 2004 09:53:05 -0400	[thread overview]
Message-ID: <4n1xljw472.fsf@lifelogs.com> (raw)
In-Reply-To: <m3sme0h5yy.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 16 May 2004 15:11:33 +0200")

On Sun, 16 May 2004, larsi@gnus.org wrote:

> Ted Zlatanov <tzz@lifelogs.com> writes:
> 
>> Could someone please clue me in as to how to fill in the missing
>> data in gnus-newsgroup-data, or tell me why gnus-newsgroup-unseen
>> is returning invalid article numbers?
> 
> Hm...  that list is computed as follows:
> 
>     (setq gnus-newsgroup-unseen
> 	  (gnus-inverse-list-range-intersection
> 	   gnus-newsgroup-articles gnus-newsgroup-seen))))
> 
> Those should be all valid article numbers, I'd have thought.

Correction: they are *valid* numbers, but the *data* in
gnus-newsgroup-data for them is nil.

I use this version of spam-fetch-article-header now, which fixes
that problem:

(defun spam-fetch-article-header (article)
  (save-excursion
    (set-buffer gnus-summary-buffer)
    (gnus-read-header article)
    (nth 3 (assq article gnus-newsgroup-data))))

I hope this is the right approach.

Ted



  reply	other threads:[~2004-05-17 13:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 17:17 Ted Zlatanov
2004-05-16 13:11 ` Lars Magne Ingebrigtsen
2004-05-17 13:53   ` Ted Zlatanov [this message]
2004-05-17 15:13     ` Lars Magne Ingebrigtsen
2004-05-17 15:11       ` Ted Zlatanov
2004-05-17 17:12         ` Lars Magne Ingebrigtsen
2004-05-17 18:59           ` Ted Zlatanov
2004-05-17 19:32             ` Lars Magne Ingebrigtsen

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=4n1xljw472.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).