[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mutt-users
Subject:    Re: attachments in Mutt
From:       "Mark H. Wood" <mwood () IUPUI ! Edu>
Date:       2014-06-26 12:57:26
Message-ID: 20140626125726.GA2117 () IUPUI ! Edu
[Download RAW message or body]


On Thu, Jun 26, 2014 at 09:14:02AM +1000, Cameron Simpson wrote:
> On 24Jun2014 20:43, Martin Vegter <martin.vegter@aol.com> wrote:
> >But all that said, should not a plain message (i.e. text body without
> >attachments) be treated by mutt as such?
> 
> Well, it is treated the same as other, more complex, types of messages...
> 
> >I am asking because when sending a message from Mutt, after I have
> >composed the message in my editor and am now in the "compose" menu, I
> >see the header (recepient, subject, ...) and below I see my message body
> >as attachment.
> >
> >Is this a good conceptual approach, to treat everything as attachment?
> 
> Since you can add an attachment from that view, I would be inclined to argue 
> "yes".
> 
> >I find this quite illogical and unintuitive. AFAIU, this is specific to
> >mutt, and does not have anything to do with any email standard.

I think you will find it has a lot to do with MIME.  The list may be
titled "attachments" but what it seems to be in reality is MIME
entities.  If that is so, then this behavior makes perfect sense.
There is no such thing as a "plain message" in MIME; the closest thing
would be a message containing a single text/plain entity.

> >When I send an email via telnet, I simply type my message after DATA,
> >and terminate with  <CR><LF>.<CR><LF>. No attachment is ever involved.
> 
> Or editing. You might be able to configure mutt to send as soon as
> you quit the edit mode with the same degree of control. I haven't
> tried.
> 
> Personally I prefer mutt's current behaviour. I use the "edit" mode to look at 
> the message text and that is what mutt drops me directly into when I start a 
> new message ("set autoedit=yes").
> 
> Outside the edit mode, I am more interested in the message structure and 
> control (headers, attachements, if any, send/quit etc).

You are not alone.  I choose Mutt because it doesn't try to hide what
it is doing for me or limit what I can do with it.

-- 
Mark H. Wood, Lead System Programmer   mwood@IUPUI.Edu
Machines should not be friendly.  Machines should be obedient.

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]