From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] mutt's auto_view and alternative_order
Date: Tue, 03 Jul 2007 15:08:04 -0700 [thread overview]
Message-ID: <1183500484-sup-7622@south> (raw)
In-Reply-To: <1181834033-sup-8054@mona>
Excerpts from jeff.covey's message of Thu Jun 14 08:32:09 -0700 2007:
> something i'm really missing from mutt is the auto_view setting for mime
> types.
[snip]
> 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.
Yup, I agree that this is a highly desirable thing. I'm going to try and
handle as much of this type of thing as possible through the
aforementioned hook system. It definitely won't happen for the next
release, though.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-07-03 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 15:32 jeff covey
2007-07-03 22:08 ` William Morgan [this message]
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=1183500484-sup-7622@south \
--to=wmorgan-sup@masanjin.net \
/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