Ken Hornstein <kenh@pobox.com> wrote: >> to my scan arguments, and it's close, but not yet what I want. >> Ideally, I just want what's in <> of the List-Id:, and I'd be happy with the >> first 16 characters only. But I can't see a way to get that. So I'd settle >> for the last 16 bytes of the entire header, but I can't get that either. > Hmmm. I just looked at regcomp()/regexec(), and it sure seems pretty easy > to make a format function that could do a regular expression substitution > on the str register. Like ... > %(void{list-id})%(regsub /<\([^.]+\)/[\1]/) > Would do what you want, I'd think. I can't promise that would appear soon > but it at least it doesn't seem hard. yes, I think it would work. if there was something to treat the header as From/To:-like (while not insisting on presence of @) and just pull out whatever was in <>, if there was something, that might actually work better, as if there is no "<", then it would just return the string that was there. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | IoT architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
signature.asc
Description: PGP signature
-- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Previous by Date: | [nmh-workers] vixie out, Paul Vixie |
---|---|
Next by Date: | Re: [nmh-workers] Additional things, Michael Richardson |
Previous by Thread: | Re: [nmh-workers] FSF is changing Mailman list settings unless you opt out (fwd), Ken Hornstein |
Next by Thread: | Re: [nmh-workers] FSF is changing Mailman list settings unless you opt out (fwd), Philipp |
Indexes: | [Date] [Thread] [Top] [All Lists] |