[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Nmh-workers] mh-format and components with empty content
From: |
norm |
Subject: |
[Nmh-workers] mh-format and components with empty content |
Date: |
Wed, 25 Feb 2015 06:58:46 -0800 |
My experiments indicate that mh-format, at least as applied to scan, does not
distinguish between a header with zero length content and a non-existent
header. Am I correct? I can't find any documentation saying that.
Maybe there is a standard that says that all components must have or should
have a content (what RFC 5322 calls a field body) of positive length.
In any case, is there a workaround that would let me write a format that would
treat a message with a component like
Foobar:
differently from a message without a "Foobar" component -- maybe some
legerdemain like appending 'X' and asking if the result is equal to 'X'.
I might note that
pick --Foobar ''
Selects messages having a foobar component, with or without non-empty content.
Norman Shapiro
- [Nmh-workers] mh-format and components with empty content,
norm <=
- Re: [Nmh-workers] mh-format and components with empty content, Ken Hornstein, 2015/02/25
- Re: [Nmh-workers] mh-format and components with empty content, Ralph Corderoy, 2015/02/25
- Re: [Nmh-workers] mh-format and components with empty content, Ken Hornstein, 2015/02/25
- Re: [Nmh-workers] mh-format and components with empty content, David Levine, 2015/02/25
- Re: [Nmh-workers] mh-format and components with empty content, Ken Hornstein, 2015/02/25
- Re: [Nmh-workers] mh-format and components with empty content, norm, 2015/02/26
- Re: [Nmh-workers] mh-format and components with empty content, Ken Hornstein, 2015/02/26
- Re: [Nmh-workers] mh-format and components with empty content, David Levine, 2015/02/26
- Re: [Nmh-workers] mh-format and components with empty content, norm, 2015/02/27
- Re: [Nmh-workers] mh-format and components with empty content, David Levine, 2015/02/27