From: johnbent@lanl.gov (John Bent)
Subject: [sup-talk] missing run-mailcap
Date: Thu, 24 Jan 2008 16:52:36 -0700 [thread overview]
Message-ID: <1201218489-sup-3542@tangerine.lanl.gov> (raw)
In-Reply-To: <1201216741-sup-4105@south>
Excerpts from William Morgan's message of Thu Jan 24 16:26:20 -0700 2008:
> Reformatted excerpts from John Bent's message of 2008-01-24:
> > When sup opens an attachment, it copies the attachment to
> > /tmp/sup-attachment-ID and then calls run-mailcap. But sup knows what
> > name the file was attached as. Could sup save the attachment to
> > /tmp/filename? Or at least append the extension?
>
> In 0.4 you should see the extension being preserved. Let me know if
> that's not the case.
>
> So you should be able to simply call "open" on that file, rather than
> having to use your Perl script.
>
Yep, just like you say. Although, I think I do still need to have something
in /usr/bin/run-mailcap that parses
"--action=view application/vnd.ms-powerpoint:/tmp/foo.ppt," and then execs
"open /tmp/foo.ppt." But that's much better than having to guess an extension
from the mime-type.
John
next prev parent reply other threads:[~2008-01-24 23:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 16:40 John Bent
2008-01-22 22:33 ` John Bent
2008-01-24 21:40 ` John Bent
2008-01-24 23:26 ` William Morgan
2008-01-24 23:52 ` John Bent [this message]
2008-01-25 0:17 ` William Morgan
2008-01-25 0:57 ` Grant Hollingworth
2008-01-25 4:40 ` John Bent
2008-01-26 0:35 ` John Bent
2008-01-30 17:29 ` William Morgan
2008-01-30 17:54 ` John Bent
2008-01-30 18:26 ` William Morgan
2008-01-30 18:35 ` John Bent
2008-02-03 3:01 ` William Morgan
-- strict thread matches above, loose matches on Subject: below --
2008-01-04 23:45 Giorgio Lando
2008-01-04 23:59 ` Giorgio Lando
2008-01-05 0:13 ` William Morgan
2008-01-05 1:01 ` Giorgio Lando
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=1201218489-sup-3542@tangerine.lanl.gov \
--to=johnbent@lanl.gov \
/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