<<< Date Index >>>     <<< Thread Index >>>

mutt/2402: damaged regexps in folder-hooks



>Number:         2402
>Notify-List:    
>Category:       mutt
>Synopsis:       damaged regexps in folder-hooks
>Confidential:   no
>Severity:       normal
>Priority:       medium
>Responsible:    mutt-dev
>State:          open
>Keywords:       
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 03 07:31:38 +0200 2006
>Originator:     Alain Bench <veronatif@xxxxxxx>
>Release:        1.5.10 up to CVS
>Organization:
>Environment:
>Description:

Hello ALL,

    In Mutt 1.5.10 and more, the regexp in folder-hooks can
be damaged in some circumstances, leading to false positive
matches. That seems to happen when the regexp both: Has
uppercase characters (is case-significant), and begins by an
'^' anchor.

    Example, in muttrc:

| folder-hook ^ABC$ yaddahyaddah

    ...and:

| $ cd /tmp
| $ touch nomatchABC
| $ mutt -f nomatchABC

    ...beeps and shouts:

| yaddahyaddah: unknown command

     The hook wrongly matched, as if the ^ anchor had been
lost. And Tamo's comval.9 feature confirms, the
<status-commands> function showing the hook as stored
internally:

| Status of commands:
|
| folder-hook
|   ABC$
|     yaddahyaddah

    ...no more anchor. Note this does not happen with Mutt
up to 1.5.9, nor with all-lowercase regexps.


Alain.
>How-To-Repeat:
>Fix:
>Add-To-Audit-Trail:

>Unformatted: