Re: [message scoring] Is it possible to ... ?
- To: mutt-users@xxxxxxxx
- Subject: Re: [message scoring] Is it possible to ... ?
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Tue, 24 Mar 2009 10:15:55 -0500
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date :from:to:subject:message-id:references:mime-version:content-type :in-reply-to; s=default; bh=fIOWWC/KQznasFlrc6w0wQ49s5M=; b=bYPB qsWZ++HHr+q3wALMH2pjuDEwZwzY1pRxGsnFfScTCc799xjkHb77hdjad5qCfzjY svFBdt3zQnqksxEog+CeIgI6H9Crz3YJQA9r+e6h2QhwDfwcD2WH15D4ExMYEGAv yM06PYmuc83ikn4ssuLkqCZV1wDmm5NpnZsCDdk=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=LwgRAQPJN03fvjqMDzjvlchzsp3YRb1Vr/gkYoQbDyF3iUtYMO7W/Lj2CX3JAh05potmoBZDNlI2rWzq/oORw7N0TBMFpG6DkoFQ/5y1iomTG8hjx92KWHjxlv6NxOHpJAnEKIVzMHN8qAeeOY+uIuhMs6f2KZMa77PFMr/ApEY=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:OpenPGP:User-Agent;
- In-reply-to: <20090324143005.GA6079@xxxxxxxxxxxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- Openpgp: id=CA8E235E; url=http://www.memoryhole.net/~kyle/kyle-pgp.asc; preference=signencrypt
- References: <20090324114159.GB3329@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20090324143005.GA6079@xxxxxxxxxxxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.19 (2009-03-15)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, March 24 at 03:30 PM, quoth Michael Tatge:
>Is it working? Somehow.
>If I manually enter the score it works. If I put the line in muttrc it's
>not. Even if I source that file in a folder-hook it seems the message
>parsing comes too late for the score to work. Bug?
It's probably an ordering problem: the score is calculated *before*
the mailbox is sorted (so that it can be used as a sorting mechanism
or displayed), and yet thread relationships are established as *part*
of sorting the mailbox and so cannot be used until *after* the mailbox
is sorted. And *after* the mailbox is sorted, the scores are not
re-calculated unless you enter in some new ones.
So, if you put in your scores as part of a folder-hook or as part of
your muttrc, those patterns are evaluated before thread relationships
between messages have been established. However, if you type your
scores in manually, while looking at a sorted mailbox, they are being
evaluated AFTER thread relationships have been established.
My guess is that those scores wouldn't do *anything* if you first
sorted your mailbox by date-received (i.e. if you didn't sort by
threads).
I think this is probably an intentional design flaw, as weird as that
sounds. Mutt doesn't figure out thread relationships if it doesn't
have to, because doing so is (or once was) computationally expensive
and requires analyzing all messages in the mailbox. So the mutt
designers put off doing that calculation until the last possible
moment: sorting. Unfortunately, this means that stuff like
this---scoring and anything else that happens BEFORE messages are
sorted (e.g. things triggered by folder-hooks)---*CANNOT* get access
to that thread-relationship information. Nor can they get access to
that thread-relationship information if the thread-based sort doesn't
happen (i.e. if you've sorted your messages in some other way).
You probably want to try to sweet-talk the mutt developers into
re-evaluating scores after the thread-relationships are established
(which, of course, has the potential to force the messages to be
re-sorted; consider what happens if sort_aux=score). Ideally,
thread-relationships would be figured out independently of sorting...
but I wouldn't hold my breath on that one.
~Kyle
- --
It has been my experience that folks who have no vices have very few
virtues.
-- Abraham Lincoln
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAknI+SsACgkQBkIOoMqOI15TOwCg97uYgi6L9wdQtZC+fO6PqmHy
Y9IAoIKAiQyNhxXclDYBGjpkQtyOTXaO
=oJhN
-----END PGP SIGNATURE-----