True. But at the moment, lets say that I add some enriched text codes here. OK, so vim does nothing with that. But I then type ":set filetype=.." (edit: I WAS initially writing this as markdown, but thought enriched text would illustrate my point better. Vim doesn't seem to handle enriched text. Emacs does, apparently, though) and hurrah, vim now shows that as bold. Yay, I'm composing my email with style!
But my point is that, at the moment, only the editor knows that I am writing in text/enriched. When I quit out, the message will be set as text/plain and no-one will see my beautiful emphasis!
What I can do, though, and I shall for this message, is set the MIME type to text/enriched. That tells recipients that my message needs interpretation.
> >> In HTML that could be <spanstyle="font-weight:bold">bold</span.in>> LaTeX, it would be \textbf{bold}. But in markdown, it's simply >> **bold**. >> >> A good LML would have a MIME type associated with it (I see that >> markdown does, but reStructuredText doesn't, for example), so it can >> either be viewed (as source) in the pager or rendered (as presentation >> form) by a mailcap entry. > >Is it necessary to send the body as an attachment in order to awaken >that mime stuff?
I'm only a user of mutt, but it is my understanding that mutt always uses MIME. MIME parts can have two dispositions: attachment or inline. The body, detached signatures (as added by mailing lists) etc are usually inline while files sent with the message are attachments.
My understanding is that mutt composes a message by invoking an editor on a temporary file. That temporary file is then added to the MIME tree with content-type:text/plain and content-disposition:inline. For demonstration purposes, this message will have one MIME part of content-type:text/enriched and content-disposition:inline.
Let's see how this works.
> >When I had to pretty-font a report for management over a decade ago, I >composed it in vim, then performed a fontification in openoffice, and >gave them a M$-compatible attachment. Problem fixed. > >Erik > >-- >HTML is not email, and email doesn't contain HTML, so please turn HTML >formatting OFF in your email client. We have filters in place that will >reject your message if your posting contains HTML. > - http://gpl-violations.org/mailinglists.html
-- For more information, please reread.
signature.asc
Description: PGP signature
