From: johnbent@lanl.gov (John Bent)
Subject: [sup-talk] missing run-mailcap
Date: Fri, 25 Jan 2008 17:35:17 -0700 [thread overview]
Message-ID: <1201307667-sup-2659@tangerine.lanl.gov> (raw)
In-Reply-To: <1201235901-sup-7426@tangerine.lanl.gov>
Excerpts from John Bent's message of Thu Jan 24 21:40:08 -0700 2008:
> Excerpts from Grant Hollingworth's message of Thu Jan 24 17:57:50 -0700 2008:
> > * William Morgan [Thu Jan 24 19:17:17 -0500 2008]:
> > > If open is a standard OS X command, then I will add some code to
> > > auto-detect it at some point.
> >
> > It is. Unfortunately, you can tell it which application to use, but
> > not which MIME type.
>
> True, but if it has the correct extension (which it does in 0.4), you
> don't need to tell it anything.
>
> That's great that I don't need to fake run-mailcap since there's a hook.
>
The hook works (system "open \'#{filename}\'"), but sup thinks it is failing.
I get a message saying view failed, displaying as text. Maybe it should
be (! system "open \'#{filename}\'") ? Also, I added the \' because I noticed
before that sometimes filename has spaces in it and then open won't work.
John
next prev parent reply other threads:[~2008-01-26 0:35 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
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 [this message]
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=1201307667-sup-2659@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