From: Mark Alexander <marka@pobox.com>
To: Tero Tilus <tero@tilus.net>
Cc: Sup developers <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] How to deal with HTML attachments?
Date: Thu, 12 May 2011 09:21:40 -0400 [thread overview]
Message-ID: <1305206411-sup-2216@bloovis.org> (raw)
In-Reply-To: <1305188427-sup-5666@tilus.net>
Excerpts from Tero Tilus's message of Thu May 12 04:30:39 -0400 2011:
> I run sup screened in a vps box, so mailcapping html to browser is not
> an option for me.
I also run sup in screen, sometimes from a remote system via ssh, so
that's why I chose w3m as the mailcap'd browser.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-05-12 13:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 13:53 Steve
2011-05-11 14:13 ` Mark Alexander
2011-05-11 14:59 ` Steve
2011-05-11 15:24 ` Mark Alexander
2011-05-11 14:15 ` Patrick Totzke
2011-05-11 15:40 ` Steve
2011-05-11 14:30 ` Matías Aguirre
2011-05-12 8:30 ` Tero Tilus
2011-05-12 13:21 ` Mark Alexander [this message]
2011-05-13 7:39 ` Tero Tilus
2011-05-13 9:55 ` Patrick Totzke
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=1305206411-sup-2216@bloovis.org \
--to=marka@pobox.com \
--cc=sup-devel@rubyforge.org \
--cc=tero@tilus.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