most-recent-date sorting and broken date strings in ognus-0.05

most-recent-date sorting and broken date strings in ognus-0.05

[raeburn]

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

Re: most-recent-date sorting and broken date strings in ognus-0.05

[Lars Magne Ingebrigtsen]

raeburn@raeburn.org writes:

> 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.

There was an error in the error handling in
`gnus-thread-latest-date'.  Things should work better now. 

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen