Ken wrote: > Well, let me make this alternate proposal: > > - "attach" adds Nmh-Attachment headers as per usual. Maybe we'll add > something like: "attaching foo.pdf to message as application/pdf" so > the user can see what MIME type is being used (really, that's all > I care about). > > - You can add or not add mhbuild directives to the message if you want. > > - If you add mhbuild directives, you can run "mime" (also, you can run > "mime" even if you don't). mhbuild will be in charge of processing > Nmh-Attachment headers.
> - If you try to "attach" after a "mime", you get an error. > > - send runs "mhbuild -auto -nodirectives". > > How does that look? More code rework, but it feels better. Also, > with this I think it actually accomplishes what you want (attach + > inspection). I like it. One question: would it make sense to put the entire mhbuild directive in the Nmh-Attachment header instead of just the path? Users could then edit it as they wish. David _______________________________________________ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers
