[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: Jon Steinhart
Subject: Re: [Nmh-workers] Conflict between "mime" command and attach
Date: Wed, 11 Dec 2013 08:00:39 -0800

Ralph Corderoy writes:
> Hi Jon,
> > > No, sorry, when I said "edit" I was referring to a whatnow-entry to
> > > put me back in vi so I can read-only peruse the outcome of "mime".
> > > My intent is always to have "mime" do the work;  if something's not
> > > right I go back to pre-"mime" and fix it because mhbuild could
> > > always do want I want AIUI.
> > 
> > Do the big MUAs let you do this?  Can you look at post-MIME stuff in
> > thunderbird?  Or do you just attach things and be happy with the
> > results>
> They do not.  But then I can only attach a file using their simplistic
> GUI and hope they get everything they choose right, e.g. text/plain v.
> message/rfc822, and miss out on the chance to specify the character
> encoding or give a content description.  That's one reason why I don't
> use them and prefer nmh.  (Though I don't think I can set the
> content-disposition's modification-date?)

My point was that most of the rest of the world gets by without this level
of control and it works.  Makes me wonder if there is some defect in the
way that nmh works that keeps things from working.
> > This is why I suggested having some optional arguments on the attach
> > header and attach command.
> Sorry, to do what?  Memory's going.

I know the problem.  Maybe we need "attach foo.jpg -type image/png" that
would make an attachment header with the -type option on it so that you
could control the picky details.

At some level, this is adding mhbuild options to attach which doesn't bug
me a lot since attach invokes mhbuild anyway.  Of course, once the door is
open for one option then *someone* on this list will want all of them.  And
then there's the error handling...

BTW, while I don't feel the need for it, attach could check for a valid file
and do any additional argument checking before returning to the whatnow prompt.
Maybe that would help.  Maybe "attach -check" would report the automatically
selected MIME types.

>From my standpoint, the biggest issues are combining forwarding or replying to
MIME messages and then adding attachments.  I'd prefer that we really thought
about how to fix this; I'd rather not add a third wart to the first two.


reply via email to

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