[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] Thoughts: header/address parsing
From: |
norm |
Subject: |
Re: [Nmh-workers] Thoughts: header/address parsing |
Date: |
Tue, 05 Aug 2014 06:07:46 -0700 |
Ken Hornstein <address@hidden> writes
>>One example: Get the effective content part of an 'X-Spam-Status" header.>
>That program already exists today.
>
>% scan -width 9999 -format '%{x-spam-status}' messages ....
>
>should do what you want, I think.
If I replace "x-spam-status" by "to", and there are multiple "To:" fields,
I'm not sure what I want. I think I want each addressee on a separate line.
But whatever I want,
% scan -width 9999 -format '%{to}' messages ...
does not give me what I want. Parsing its output, distinguishing commas
used as delimiters, and commas within quotes, is not quite trivial.
Norman Shapiro
- [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/02
- Re: [Nmh-workers] Thoughts: header/address parsing, Ralph Corderoy, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, norm, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, Lyndon Nerenberg, 2014/08/03
- Re: [Nmh-workers] Thoughts: header/address parsing, norm, 2014/08/04
- Re: [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/04
- Re: [Nmh-workers] Thoughts: header/address parsing, Ralph Corderoy, 2014/08/05
- Re: [Nmh-workers] Thoughts: header/address parsing,
norm <=
- Re: [Nmh-workers] Thoughts: header/address parsing, Jon Fairbairn, 2014/08/06
- Re: [Nmh-workers] Thoughts: header/address parsing, Ralph Corderoy, 2014/08/06
- Re: [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/06
- Re: [Nmh-workers] Thoughts: header/address parsing, Lyndon Nerenberg, 2014/08/04
- Re: [Nmh-workers] Thoughts: header/address parsing, Ken Hornstein, 2014/08/04
- Re: [Nmh-workers] Thoughts: header/address parsing, Lyndon Nerenberg, 2014/08/04