From: decklin@red-bean.com (Decklin Foster)
Subject: [sup-talk] run-mailcap weirdness
Date: Sun, 26 Oct 2008 14:48:41 -0400 [thread overview]
Message-ID: <1225046594-sup-8381@gillespie.rupamsunyata.org> (raw)
Viewing HTML attachments fails for me. It turns out that Debian's mailcap
falls over if standard output is not a terminal (see below).
I don't know if this is right, but removing the redirection makes it work
for me (I've committed this to decklins-clone at Gitorious). What was the
original rationale for /dev/null-ing this? I noticed if you set the mailcap
command to something that just prints text (no pager) it blips by
instantaneously in Sup. So, unless we can snarf the output for logging
purposes, maybe it is better to just let it reach the terminal?
Example mailcap lossage:
$ echo hello | /usr/bin/run-mailcap --debug=1 --action=view text/plain:- >/dev/null
- parsing parameter "--action=view"
- parsing parameter "text/plain:-"
- file "-" does not exist -- assuming mime-type specification of "text/plain"
- Reading mailcap file "/home/decklin/.mailcap"...
- Reading mailcap file "/etc/mailcap"...
Processing file "-" of type "text/plain" (encoding=none)...
- checking mailcap entry "text/plain; less '%s'; needsterminal"
- program to execute: less '%s'
- no terminal available for rule (needsterminal)
- checking mailcap entry "text/plain; more '%s'; needsterminal"
- program to execute: more '%s'
- no terminal available for rule (needsterminal)
- checking mailcap entry "text/*; less '%s'; needsterminal"
- program to execute: less '%s'
- no terminal available for rule (needsterminal)
- checking mailcap entry "text/*; more '%s'; needsterminal"
- program to execute: more '%s'
- no terminal available for rule (needsterminal)
Error: no "view" rule for type "text/plain" passed its test case
(for more information, add "--debug=1" on the command line)
--
things change.
decklin at red-bean.com
next reply other threads:[~2008-10-26 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 18:48 Decklin Foster [this message]
2008-10-28 2:17 ` 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=1225046594-sup-8381@gillespie.rupamsunyata.org \
--to=decklin@red-bean.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