Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Patrick Totzke <patricktotzke@googlemail.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] How to deal with HTML attachments?
Date: Fri, 13 May 2011 10:55:17 +0100	[thread overview]
Message-ID: <1305280248-sup-3289@brick> (raw)
In-Reply-To: <1305272083-sup-4650@tilus.net>


[-- Attachment #1.1: Type: text/plain, Size: 653 bytes --]

Excerpts from Tero Tilus's message of Fri May 13 08:39:34 +0100 2011:
> Mark Alexander, 2011-05-12 16:21:
> > 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.
> 
> I do w3m too.  Most (~90%) of the time it does exactly what I want,
> but sometimes (say with images, pdf:s and strangely laid out html
> documents) an url to the document is a must.

I can highly recommend lynx'x dump mode for inline html: it 
produces a "references" suffix which displays all URI's from the
links in the document. This works great con combination with 
urxvt's url-select script.
/p

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

      reply	other threads:[~2011-05-13  9:55 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
2011-05-13  7:39     ` Tero Tilus
2011-05-13  9:55       ` Patrick Totzke [this message]

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=1305280248-sup-3289@brick \
    --to=patricktotzke@googlemail.com \
    --cc=sup-devel@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