From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] mailcap for os x
Date: Tue, 15 Jan 2008 19:20:45 -0800 [thread overview]
Message-ID: <1200453317-sup-5958@south> (raw)
In-Reply-To: <1200414674-sup-1175@spooky.local>
Reformatted excerpts from Grant Hollingworth's message of 2008-01-15:
> Excerpts from William Morgan's message of Thu Dec 27 13:50:26 -0500 2007:
> > I'd willingly accept a patch to hook into Attachment#view! and allow
> > overriding of the default run-mailcap behavior.
>
> Sure, but I don't know of the best way to do that. It wouldn't be like
> other hooks, because it has to replace behaviour and not just
> supplement it.
That's not a problem. There are plenty of hooks that override default
behavior if they're present, but do nothing if not. The quoteline one
Marcus just submitted is a good example.
> Lots of systems don't have run-mailcap(1). Probably we should port it
> and push it out as a gem that Sup depends on.
If we want to make some kind of a mailcap-parsing gem, there's a Python
version that is probably more directly portable:
http://docs.python.org/lib/module-mailcap.html
Ruby doesn't seem to have any mailcap library, so this would be a good
contribution to the community, especially if it played nicely with
MIME::Types.
Of course, mailcap only gets you Unix systems. Or does OS X use
mailcaps? I imagine for Windows you would need some hideous registry
parsing thing that I'm not even close to writing...
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-01-16 3:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 16:22 Grant Hollingworth
2007-12-27 18:50 ` William Morgan
2008-01-15 16:34 ` Grant Hollingworth
2008-01-16 3:20 ` William Morgan [this message]
2008-01-16 3:39 ` William Morgan
2008-01-16 4:06 ` 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=1200453317-sup-5958@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