On 24Jun2014 20:43, Martin Vegter <[email protected]> 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.
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).
Cheers,
Cameron Simpson <[email protected]>
