From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: problems with gnus-newsgroup-unseen and gnus-newsgroup-data
Date: 17 May 2004 11:11:09 -0400 [thread overview]
Message-ID: <4nsmdzjdgy.fsf@lifelogs.com> (raw)
In-Reply-To: <m3k6zbytl8.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 17 May 2004 17:13:55 +0200")
On Mon, 17 May 2004, larsi@gnus.org wrote:
> "Ted Zlatanov" <tzz@lifelogs.com> writes:
>
>> 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.
>
> Hm. If the header is present in the summary buffer, then it should
> also be present in `gnus-newsgroup-data'...
I kept getting errors when I assumed that. I'm not sure what's the
cause, but headers are often missing in the newsgroup-data. It
doesn't show up often, maybe 5% of the time, and I couldn't find a
pattern to it (except that it was repeatable when you re-entered the
group).
Maybe it's threads-related? I don't know. Anyhow, if you need me to
show you examples of this problem I can, but I can't trace the root
cause of why the headers are nil. I tried that and everything looked
OK last time.
Oh, there was a very recent fix for gnus-dup-unsuppress-article which
dealt with this also, because the mail header would be nil there too.
Ted
next prev parent reply other threads:[~2004-05-17 15:11 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
2004-05-17 15:13 ` Lars Magne Ingebrigtsen
2004-05-17 15:11 ` Ted Zlatanov [this message]
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=4nsmdzjdgy.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).