[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] Conflict between "mime" command and attach

From: Ken Hornstein
Subject: Re: [Nmh-workers] Conflict between "mime" command and attach
Date: Sat, 07 Dec 2013 10:52:05 -0500

>Why wouldn't that be reasonable?  The logic would be simpler:
>In WhatNow?
>- If you run "mime", run mhbuild on the draft.
>- If you "attach", add the appropriate mhbuild directive.  Do not do
>  this if there is a MIME-Version header.
>In post(8):
>- Run "mhbuild -auto -nodirectives".

The problem here is that if you use -nodirectives, then the directives that
attach put in the draft wouldn't be executed.

Ralph said:

>It would also mean I could "attach", then "edit" to look at it, perhaps
>embellish, then "mime" to process it, then "edit" again to check things
>over before I "send"

You can do this now; if you attach, you can edit the draft and adjust the
pseudo-header that attach adds.

The problem with using mhbuild directives is that it creates special
semantics for the message body; specifically, you can't have lines that
start with '#' without special escaping.  That's fine for people who
want to do that, but I think it's a poor solution for the average user.

I was thinking of a special #attach directive that used the same logic
as "attach"; instead of:

#image/jpeg {attachment} /tmp/foo.jpg

You'd just have:

#attach /tmp/foo.jpg

To provide an easier-to-use MIME experience that covers the common case.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]