From: raeburn@raeburn.org
Subject: most-recent-date sorting and broken date strings in ognus-0.05
Date: Thu, 06 Jun 2002 21:26:11 -0400 [thread overview]
Message-ID: <tx1y9drhob0.fsf@mit.edu> (raw)
I've been trying to use gnus-thread-sort-by-most-recent-date, and
aside from the gathered-threads problem I reported before, one other
problem keeps coming up.
I have a few messages with bad date lines. When ietf-drums-parse-date
hits them, encode-time reports an error, the sorting blows out, and I
get an empty summary buffer.
"2/19/2002" by "Spyder Mailer 1.0"
"Sun, 2 Jan 100 14:39:12 EST" and the like by elm
The first is spam, and ELM has since been fixed, but the messages are
still in my mailbox. I'd rather not resort to hand-editing the
messages every time a broken message comes in.
Using gnus-summary-sort-by-date doesn't have this problem, because it
uses gnus-date-get-time. Indeed, things just seem much happier if I
fset mail-header-parse-date to a function that uses
gnus-date-get-time. Is there any reason not to redefine
ietf-drums-parse-date to use it?
Ken
next reply other threads:[~2002-06-07 1:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 1:26 raeburn [this message]
2002-12-30 20:57 ` 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=tx1y9drhob0.fsf@mit.edu \
--to=raeburn@raeburn.org \
/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).