From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [PATCH] change opening attachements on darwin to use open instead of run-mailcap
Date: Fri, 30 Oct 2009 15:07:19 -0700 [thread overview]
Message-ID: <1256940409-sup-4411@masanjin.net> (raw)
In-Reply-To: <4AE8C073.404@GoodCoffee.ca>
Reformatted excerpts from Jonah's message of 2009-10-28:
> I've been working on getting sup to work in MacOSX (darwin). MacOSX has a
> special command (open) for opening files - there is no support for mailcap.
> This patch uses case to run the appropriate command depending on the
> architecture used.
Branch no-mailcap-on-darwin, merged into next. Thanks!
> I still haven't gotten sup to send mail yet,.. so more patches for
> MacOSX will probably be forthcoming. :)
Great, glad to have them.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-10-30 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 22:06 Jonah
2009-10-30 22:07 ` William Morgan [this message]
2009-10-30 23:13 ` Jon Dugan
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=1256940409-sup-4411@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@rubyforge.org \
/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