From: flips@luminated.net (Filip Stokkeland)
Subject: [sup-talk] /usr/bin/run-mailcap
Date: Thu, 7 May 2009 13:58:02 +0200 [thread overview]
Message-ID: <24cc29320905070458g7b970ea4rbfcc469d6afc3a3d@mail.gmail.com> (raw)
In Sup, installed on a RHEL 5.1 with EPEL, using gems, when I select
f.ex. html attachments, I just get an error that view doesn't work and
I get the plain text. A quick grep in the code reveals this:
lib/sup/message-chunks.rb: cmd = "/usr/bin/run-mailcap
--action=view '#{@content_type}:#{path}' 2>/dev/null"
I can't find run-mailcap on this RedHat installation. "yum
whatprovides" didn't help and the mailcap package had no such file
installed:
# rpm -ql mailcap
/etc/mailcap
/etc/mime.types
/usr/share/man/man4/mailcap.4.gz
Maybe run-mailcap a Debian/Ubuntu thing? (I'll be back on my regular
ubuntu installation soon enough anyway, just using a lab machine right
now.) In Mutt I don't believe I did anything except use my default
.mailcap ...
Cheers.
--
Filip
next reply other threads:[~2009-05-07 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 11:58 Filip Stokkeland [this message]
2009-05-07 13:07 ` William Morgan
2009-05-07 13:21 ` Ben Walton
2009-05-07 15:29 ` Mark Alexander
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=24cc29320905070458g7b970ea4rbfcc469d6afc3a3d@mail.gmail.com \
--to=flips@luminated.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