ken wrote:
part text/plain 1020
i don't recall us ever discussing the possibility of making the '#'
character that introduces mhbuild directives configurable by the user.
for instance, if the leading character were '}', i don't think i would
ever have a conflict with "real" text.
interpretation of those directives is strictly within mhbuild,
correct? no leakage into other mh commands?
There used to be some leakage; for example, the old attach implementation
would parse the Nmh-Attachment headers and then create mhbuild directives.
I am not sure there is any leakage now. But I am not in love with the idea
of changing the leading character, because that opens the box for "how should
we do MIME composition, anyway?" Which is not going to be easy. As a
i guess i'm not sure how letting a user change the prefix character on
the existing mechanism would make that worse.
(and i'm not talking about 1.6.)
paul
comparison, MH-E has it's own syntax which seems to be XML-based. I have
no idea if it's better or worse than mhbuild.
--Ken
_______________________________________________
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
----------------------
paul fox, pgf@foxharp.boston.ma.us (arlington, ma, where it's 71.2 degrees)
_______________________________________________
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers