[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: sorting uniquely by message-id
From: |
Ralph Corderoy |
Subject: |
Re: sorting uniquely by message-id |
Date: |
Mon, 21 Sep 2020 15:56:40 +0100 |
Hi,
Wolfgang wrote:
> > The pick man page doesn't present this quite as clearly as it could,
> > but when it refers to "--component", "component" means "any header
> > field name". So I think what you want is: "pick --message-id .*".
> > (The double hyphen is important.)
>
> Indeed, this fixes the problem (of course we have to escape the '.*'
> tp prevent the shell from expanding it).
My suggestion used ‘--message-id 'z*'’. Its approach uses MH sequences,
each a fast set implemented using a bitmap, with a loop iterating for
each distinct message-ID field.
https://lists.nongnu.org/archive/html/nmh-workers/2020-09/msg00008.html
--
Cheers, Ralph.
- Re: sorting uniquely by message-id, (continued)
- Re: sorting uniquely by message-id, Ralph Corderoy, 2020/09/19
- Re: sorting uniquely by message-id, spaceman, 2020/09/19
- Re: sorting uniquely by message-id, kat, 2020/09/19
- Re: sorting uniquely by message-id, Ralph Corderoy, 2020/09/20
- Re: sorting uniquely by message-id, Krullen Van De Trap, 2020/09/20
- Re: sorting uniquely by message-id, Wolfgang Denk, 2020/09/21
- Re: sorting uniquely by message-id, Krullen Van De Trap, 2020/09/21
- Re: sorting uniquely by message-id, Wolfgang Denk, 2020/09/21
- Re: sorting uniquely by message-id, Paul Fox, 2020/09/21
- Re: sorting uniquely by message-id, Wolfgang Denk, 2020/09/21
- Re: sorting uniquely by message-id,
Ralph Corderoy <=
- Re: sorting uniquely by message-id, Ralph Corderoy, 2020/09/21
- Re: sorting uniquely by message-id, Wolfgang Denk, 2020/09/21
Re: sorting uniquely by message-id, Michael Richardson, 2020/09/19
Re: sorting uniquely by message-id, e40 / envoy510, 2020/09/20