Re: Stupid regexp tricks

2014-12-10 Thread John Long
Hi, On Tue, Dec 09, 2014 at 05:08:22PM -0600, David Champion wrote: > * On 09 Dec 2014, John Long wrote: > > The messages seem to all have message-ids in the form > > > > bunchofch...@m.something.com > > You'll need to be much more specific if you want help writing a matching > regex. Is "some

Re: Stupid regexp tricks

2014-12-10 Thread John Long
On Tue, Dec 09, 2014 at 04:17:00PM -0500, Nathan Stratton Treadway wrote: > On Tue, Dec 09, 2014 at 20:39:16 +, John Long wrote: > > score '~i @m\..*\.com' - > > > > matches on > > > > Message-ID: <5486ad9f.8186460a.0aee.1...@mx.google.com> > > You want the actual regex

Re: Stupid regexp tricks

2014-12-10 Thread David Champion
* On 10 Dec 2014, John Long wrote: > > On Tue, Dec 09, 2014 at 05:08:22PM -0600, David Champion wrote: > > * On 09 Dec 2014, John Long wrote: > > > The messages seem to all have message-ids in the form > > > > > > bunchofch...@m.something.com > > > > You'll need to be much more specific if you

Re: Stupid regexp tricks

2014-12-10 Thread John Long
On Wed, Dec 10, 2014 at 06:50:30AM -0600, David Champion wrote: > OK, I see what I'm missing now: it's the "m" vs "mx". You're right, > getting the regex right for this one will be enough -- for now. But > it turns out that more than one site uses m.*.com hostnames, so > you'll be back in this p

Re: Stupid regexp tricks

2014-12-10 Thread John Long
On Tue, Dec 09, 2014 at 04:28:53PM -0500, Nathan Stratton Treadway wrote: > On Tue, Dec 09, 2014 at 16:17:00 -0500, Nathan Stratton Treadway wrote: > > but mutt also processes backslashes when it is parsing the command line > > defining the expresion -- so you may need to quote the backslashes. >