Re: Getting new mail really slow with nnml marks

[Simon Josefsson <jas@extundo.com>]

David Z Maze <dmaze@MIT.EDU> writes:

> Yes, it does.  My theory is that this happens because
> nnml-marks-changed-p tests whether the value gnus-gethash returns is
> eq to the modtime returned by file-attributes; since they're
> presumably not going to be the same object (I'd expect file-attributes
> to return a new list every time), you want to test equality with
> equal, rather than eq.

Aha!  Right.

> If I do this, then I get the whole updating-marks thing run at
> startup, but not at all afterwards when I run 'g' (even if there is
> new mail or I touch a .marks file).  Is this expected?

If you touch a .marks file, `nnml-marks-changed-p' must return
non-nil!  New mail shouldn't matter, but iff the .marks file is
modified n-m-c-p return non-nil.

But the change look right, can you find out why n-m-c-p doesn't return
non-nil when you touch the .marks file?