From: jeff.covey@pobox.com (jeff covey)
Subject: [sup-talk] mutt's auto_view and alternative_order
Date: Thu, 14 Jun 2007 11:32:09 -0400 [thread overview]
Message-ID: <1181834033-sup-8054@mona> (raw)
something i'm really missing from mutt is the auto_view setting for mime
types. unfortunately, so many mail user agents send out only html messages,
and they appear in sup as just a single "mime attachment" line. when you
reply to one of them, you get an empty quote of the sender's message, and
you have to go back, launch the attachment in an external viewer, copy and
paste, put the text in the reply with "> "s, etc.
it would be great if config.yaml let the user specify a list of mime types
which should have their attachments run through the .mailcap-specified
filters with copiousoutput tags, and have the results inserted into the text
of the message. i think it might be good to keep the "mime attachment" line
as well, so that hitting enter on it would launch an external viewer for the
times you want that. (mutt's documentation has a thorough section on how
they handle .mailcap; it has some good ideas.)
mutt's alternative_order is also nice. it lets you say, for example, "if
there's multipart/alternative mail with the same message as text/plain and
text/html, just show me the text/plain version." this could be handled
nicely by displaying the most-desired version as its full text and the
less-desirable ones as "mime attachment" lines.
thanks,
--
jeff covey
http://jeffcovey.net/
next reply other threads:[~2007-06-14 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 15:32 jeff covey [this message]
2007-07-03 22:08 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1181834033-sup-8054@mona \
--to=jeff.covey@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox