[nmh-workers] Flagging messages

2019-06-07 Thread Arthur Alinovi
My apologies for taking so long to respond. It was not intentional but one 
thing led to another and before I knew it more than  a week had gone by.

I’d like to thank all who responded, either directly to me or to the list.

In the end, I’ve decided not to accomplish this through nmh but rather use 
Diane Skoll’s remind program. I think it sums my needs better in the long run.

Reading through the archives it becomes clear that the people here know more 
than I ever will. To use an old cliche; most of you have forgotten more than 
I’ll ever know.

That said, again I appreciate the time people took to respond either directly 
to me or to the list/


-- 
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: [nmh-workers] Stupid 'pick' question...

2019-06-07 Thread Bakul Shah
But more often I just use grep or agrep by cd-ing to the right folder:

cd ~/Mail/
pick + -from  -and -subj  ... -seq foo
pick foo | xargs agrep -li 'this;that' | xargs scan

-- 
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: [nmh-workers] Stupid 'pick' question...

2019-06-07 Thread Bakul Shah
On Fri, 07 Jun 2019 19:00:52 -0400 "Valdis =?utf-8?Q?Kl=c4=93tnieks?=" 
 wrote:
>
> So trying to work with the linux-kernel mailing list firehose (800-1500
> messages a day), and hitting a problem with 'pick'.
>
> Am trying to match all messages from a given person with a given part of
> a subject line.
>
> pick -from  -subject '\[PATCH [45]\.[0-9]'
>
> *almost* does what I want - catch all messages that have '[PATCH 4.9]'
> or '[PATCH 4.14]'  or '[PATCH 5.0]'.  However, it *also* catches messages
> of the form 'Subject: Re: [PATCH ' which is unacceptable for the use case
> in question.
>
> So I tried an anchored search using -subject '^\[PATCH [45]\.[0-9]' but that
> results in nothing matching. So much for this from the manpage:

man pick
to see why.

-subject '^foo'
is equivalent to
-search "subject[ \t]*:.*^foo'
which won't match anything.

> Oddly enough, $ for tail-anchor seems to work:

This makes sense since
 -subj 'foo$' is
is 
-search "subject[ \t]*:.*foo$'

You can directly use search as follows:

-search 'Subject[ \t]:[ \t]*\[PATCH [45]\.[0-9]'


-- 
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers

[nmh-workers] Stupid 'pick' question...

2019-06-07 Thread Valdis Klētnieks
So trying to work with the linux-kernel mailing list firehose (800-1500
messages a day), and hitting a problem with 'pick'.

Am trying to match all messages from a given person with a given part of
a subject line.

pick -from  -subject '\[PATCH [45]\.[0-9]'

*almost* does what I want - catch all messages that have '[PATCH 4.9]'
or '[PATCH 4.14]'  or '[PATCH 5.0]'.  However, it *also* catches messages
of the form 'Subject: Re: [PATCH ' which is unacceptable for the use case
in question.

So I tried an anchored search using -subject '^\[PATCH [45]\.[0-9]' but that
results in nothing matching. So much for this from the manpage:

   A modified grep(1) is used to perform the matching, so the  full  regular
   expression  (see  ed(1))  facility  is  available  within  pattern.  With
   -search, pattern is used directly, and with the others, the grep  pattern
   constructed is:

So is ^ to anchor the search in fact unsupported?  Broken? I'm using it wrong?

Oddly enough, $ for tail-anchor seems to work:

18:56:33 0 [~/Mail/kernel-patches] scan `pick +linux-kernel last:3000 -from 
gre...@linuxfoundation.org -and -subject 'path' -list` | more
416491  *  17:38 +02  6k Greg Kroah-Hartma  [PATCH 4.14 04/69] net: 
fec: fix the clk mismatch in failed_reset path < [ Upstre
416492  *  17:38 +02  6k Greg Kroah-Hartma  [PATCH 4.14 14/69] net: 
mvneta: Fix err code path of probe < [ Upstre
416502  *  17:39 +02  6k Greg Kroah-Hartma  [PATCH 4.14 30/69] USB: 
sisusbvga: fix oops in error path of sisusb_probe < comm
416537  *  17:38 +02  6k Greg Kroah-Hartma  [PATCH 4.19 10/73] USB: 
sisusbvga: fix oops in error path of sisusb_probe < comm
416689  *  17:38 +02  6k Greg Kroah-Hartma  [PATCH 5.1 10/85] USB: 
sisusbvga: fix oops in error path of sisusb_probe < commi
18:56:52 0 [~/Mail/kernel-patches] scan `pick +linux-kernel last:3000 -from 
gre...@linuxfoundation.org -and -subject 'path$' -list` | more
416491  *  17:38 +02  6k Greg Kroah-Hartma  [PATCH 4.14 04/69] net: 
fec: fix the clk mismatch in failed_reset path < [ Upstre
18:57:08 0 [~/Mail/kernel-patches]



pgpjYVXoVMbUk.pgp
Description: PGP signature
-- 
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers