From d2c966a84866d1fb91f694a46e2b75856b1859b0 Mon Sep 17 00:00:00 2001 From: Kevin McCarthy Date: Wed, 31 May 2017 16:18:29 -0700 Subject: [PATCH] Add note about message scoring and thread patterns. (see #3947) Because scoring occurs before the mailbox is sorted, thread patterns don't work. Document a suggested workaround of pushing the score command in a folder hook. Also, fix the link target for the score command synopsis. --- doc/manual.xml.head | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/doc/manual.xml.head b/doc/manual.xml.head index 224e98ae1..e90b0d331 100644 --- a/doc/manual.xml.head +++ b/doc/manual.xml.head @@ -5066,6 +5066,17 @@ message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""' scorecommand for it to be removed. The pattern *is a special token which means to clear the list of all score entries. + + Scoring occurs as the messages are read in, before the mailbox is + sorted. Because of this, patterns which depend on threading, such as + ~=, + ~$, and + ~(), will not work by default. A workaround is to push + the scoring command in a folder hook. This will cause the mailbox to be + rescored after it is opened and input starts being processed: + +folder-hook . 'push "<enter-command>score ~= 10<enter>"' + @@ -15962,7 +15973,7 @@ folder-hook ^pop 'set read_inc=1' - score + score pattern @@ -15971,7 +15982,7 @@ folder-hook ^pop 'set read_inc=1' value - unscore + unscore -- 2.40.0