Re: Threading bugs reports
On 2005-11-11, mauro <uamlist@xxxxxxxxxxx> wrote:
> Hi All,
>
> I would like to know how I can thread automatically
> generated bugs reports from a mailing list.
> for example:
>
> ...
> 7 Nov 07 bugzilla@xxxxxxxxxxx ( 26)
> [ntp:bugs] [Bug 495] ipv4 multicast on INADDR_ANY
> silently ign
> N 8 Nov 07 bugzilla@xxxxxxxxxxx ( 27)
> [ntp:bugs] [Bug 495] ipv4 multicast on INADDR_ANY
> silently ign
> N 9 Nov 07 bugzilla@xxxxxxxxxxx ( 44)
> [ntp:bugs] [Bug 495] ipv4 multicast on INADDR_ANY
> silently ign
> 10 Nov 07 bugzilla@xxxxxxxxxxx ( 29)
> [ntp:bugs] [Bug 514] ntpd rejects local clock
>
> 11 Nov 07 bugzilla@xxxxxxxxxxx ( 32)
> [ntp:bugs] [Bug 514] ntpd rejects local clock
> 12 Nov 07 bugzilla@xxxxxxxxxxx ( 29)
> [ntp:bugs] [Bug 514] ntpd rejects local clock
> ...
>
> The subjects are the same but they are not as reply to
> previous messages.
>
> Is there any way to thread them?
You should be able to create a reply_regexp that matches those
subjects, e.g.,
set reply_regexp="^\\[ntp:bugs\\]"
and then also put
unset strict_threads
in your muttrc. If you want your reply_regexp to work for normal
"Re:" replies as well, the expression will need to be a little more
complicated. I _think_ the following will work to combine the
expression above with mutt's default, but I haven't tested it and I
seldom get mutt patterns right the first time.
set reply_regexp="^(re([\[0-9\]+])*|aw|\\[ntp:bugs\\]):[ \t]*"
HTH,
Gary
--
Gary Johnson | Agilent Technologies
garyjohn@xxxxxxxxxxxxxxx | Wireless Division
http://www.spocom.com/users/gjohnson/mutt/ | Spokane, Washington, USA