Re: How to tell GUI MUAs to show message in a fixed font?
On Sat, Apr 29, 2017 at 06:36:42PM +1000, Erik Christiansen wrote: > Impressive. Works well in mutt, too. But when it comes time to reply to > such niftiness, we might be better off hard wrapping it, to restore the > plaintext quoting - at least when multiple authors are quoted, or we > won't know what was written by Arthur, Martha, or Mo. > (Maybe the GUI world doesn't fuss much with attribution?) The GUI world largely doesn't do trimmed inline replies. They top-post without trimming. -- Ed Blackman
Re: How to tell GUI MUAs to show message in a fixed font?
On Fri, Apr 28, 2017 at 02:16:08PM +, Grant Edwards wrote: > So how, in the editor, do you tell Mutt that you've created a > multipart alternative body? Arrange for the editor to return a MIME message? Right now if you set edit_headers and manual compose a MIME message, mutt wipes out the MIME headers and leaves the MIME parts as garbage in the single text/plain part. But if mutt would examine the message returned from $editor to see whether it's a MIME message, and leave the structure intact if so, that would be a cheap way of allowing people to hook their own MIME composition systems in. People could set $editor to "markdown_mime /path/to/real/editor %s" which would call the editor with what mutt passes, but create a MIME structure with the result before handing it back to mutt. There's some complexity around what to do if $edit_headers is no (look for a minimal MIME structure with only the MIME headers and parts?), how to handle reedits (pass just the text/plain part back to $editor? pass the whole thing including MIME parts?), etc, but better than overloading $sendmail. -- Ed Blackman
Re: Rich text & Mutt [Was: How to tell GUI MUAs to show message in a fixed font?]
On Fri, Apr 28, 2017 at 08:30:03PM +1000, Erik Christiansen wrote: > Darac, I'm sorry, but that run-on corruption of email quoting is quite > unreadable. A failed experiment perhaps? If you pipe the text/enriched message part to a simple pager (eg, less), you'll see that, as described, he composed a regular email with some text/enriched markers, then changed the MIME type from text/plain to text/enriched. According to https://en.wikipedia.org/wiki/Enriched_text, a single newline in enriched text is treated like a space, thus leading to his paragraphs delimited by double-newlines being wrapped together. Since he didn't remove the quote markers, they got wrapped, too. -- Ed Blackman