Date: Thu, 20 Jun 2002 15:27:24 -0500 (CDT) From: "Brandon D. Valentine" <bandix@geekpunk.net> To: Bosko Milekic <bmilekic@unixdaemons.com> Cc: Matthew Hunt <mph@astro.caltech.edu>, freebsd-hackers@FreeBSD.ORG Subject: Re: Some small projects for mutt(1) Message-ID: <20020620152533.H753-100000@dallben.homeportal.2wire.net> In-Reply-To: <20020620161838.A24262@unixdaemons.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 20 Jun 2002, Bosko Milekic wrote: >On Thu, Jun 20, 2002 at 01:10:39PM -0700, Matthew Hunt wrote: >> This shouldn't be hard to glue together without modifying mutt itself. >> Make a little program, foo, that takes the message on stdin, passes >> it through "formail -x subject", massages it into a procmail rule, and >> appends it to some procmail rule file. The "massage" step should include >> escaping characters that have special meanings in procmail regexps, and >> adding something like (Re: *)? at the beginning of the subject when >> appropriate. Shouldn't be more than a screenful of Perl. > > Interesting. How would you have a key bound sequence in mutt set off >the script on the message, though? For instance, if I do a "ctrl+B", how >would you ensure that the Right Thing happens, without modifying mutt >code? Check out mutt2procmailrc written by my good friend timball: http://www.ghettohack.net/timball/ It rocks. Brandon D. Valentine -- http://www.geekpunk.net bandix@geekpunk.net ++[>++++++<-]>[<++++++>-]<.>++++[>+++++<-]>[<+++++>-]<+.+++++++..++ +.>>+++++[<++++++>-]<++.<<+++++++++++++++.>.+++.------.--------.>+. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020620152533.H753-100000>