#3861: mutt segfaults on scoring with ~X
------------------------+----------------------
Reporter: antonio@… | Owner: mutt-dev
Type: defect | Status: closed
Priority: major | Milestone:
Component: display | Version:
Resolution: fixed | Keywords:
------------------------+----------------------
Changes (by Kevin McCarthy <kevin@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"ba5d900a90db3e0ef97f092f685fab4253cb2ab4"
6777:ba5d900a90db]:
{{{
#!CommitTicketReference repository=""
revision="ba5d900a90db3e0ef97f092f685fab4253cb2ab4"
Disable ~X when message scoring. (closes #3861)
mutt_score_message() purposely passes a NULL context to
mutt_pattern_exec(). The idea was to block slow patterns, and the
scoring documentation notes this by saying:
"For efficiency reasons, patterns which scan information not
available in the index, such as ~b, ~B or ~h, may not be used"
~X needs the context to parse the messages (during message scoring at
least), and thus isn't suitable for message scoring either.
Block ~X from being used when the context is NULL. Add ~X to the list
of patterns noted as unusable in the message scoring documentation.
}}}
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3861#comment:3>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
