Re: viewing URLs (muttils or lynx?)
- To: mutt-users@xxxxxxxx
- Subject: Re: viewing URLs (muttils or lynx?)
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Sat, 15 Mar 2008 14:33:45 -0500
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date: from:to:subject:message-id:references:mime-version:content-type: in-reply-to; q=dns/txt; s=default; bh=QbX1TAj3wOjOXcVqU66wzDvw36 8=; b=NpoRJPn+JMNjVc5HtsypFLeVafL70kUSHQTcyZs09dbzHBEHEO7MTkUL/k hpUhdwInIIkSbYH/hQYwOA8HrwNV6ZhVaPI+JHAEv9MUWtU9kYYBq5wOcpgsPhvI JeNNO3Bu4AnmAz29Tgs1yf40qh+ev1CfKN3NHZ1q/3kbKpwH0=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=HcyTHYlBJxybz3zzUMsy4iZKAxOFjpGQB881nF0itW+LndhSuwFiaqHvzG+1ApfssnjKpmrnKSpzHWQ1Z/3KvPvtG/DSIINHnoN+MfUhjMbfuQlH0cDtNLQAgKKv3/ZAfqmjWYi7JRuQIR/P/FAklo8zNFFV5zZaw+rj30OxyY0=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:OpenPGP:User-Agent;
- In-reply-to: <20080315105230.GD4973@xxxxxxxxxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- Openpgp: id=CA8E235E; url=http://www.memoryhole.net/~kyle/kyle-pgp.asc; preference=signencrypt
- References: <20080216225208.GA443@xxxxxxxxxxxxxxxxxxx> <20080314215005.GC4973@xxxxxxxxxxxxxxxx> <20080314223413.GA10058@xxxxxxxxxxxxx> <20080315105230.GD4973@xxxxxxxxxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.17 (2008-02-27)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday, March 15 at 11:52 AM, quoth Robert Svoboda:
>> This is relatively easy to do for typical text-based <a href="URL">
>> links and links listed in text/plain email, but what about things
>> like <a href=""> links around images, or <blockquote cite="URL"> or
>> <embed src="foo" pluginspage="bar">? Or even <iframe
>> src="gotcha!">? That gets tricky fast. I wouldn't want to make it
>> impossible to access those links... but if not, how do we display
>> things? I don't know that there's a really good solution without
>> doing a full-blown html render (I'm open to being wrong).
>
> I don't get much html email anyway so for me the basic functionality
> would do the job fine. I was thinking about urifind (
> http://search.cpan.org/dist/urifind/urifind ) which is able to
> extract links from text documents (be it html, plain, whatever).
Well, that'd output your links, but wouldn't do much for identifying
their context in the text. And it can't properly handle mail that has
the delsp=yes flag set.
> As I said I don't get much html email and if it comes it's certainly
> not that advanced as to contain frames or other embedded things.
> Maybe displaying link to that content would be enough?
What, you mean transform <iframe src="foo"> into just "foo"? That's
not too bad an idea... could really muck with layout of your email,
though, especially if the iframe was just a way to insert an
advertisement (such as yahoogroups emails).
I still think that, in order to do it "right", you'd need to basically
do it within a full-blown html renderer (that way you could do things
like limit how much a given behavior will rearrange the content of the
email).
~Kyle
- --
To invent, you need a good imagination and a pile of junk.
-- Thomas Jefferson
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAkfcJJkACgkQBkIOoMqOI14rqQCdEHpVeNXLldQCcP0q998uWgJD
M+IAoJraQql9P74aO0Mcsnlep78YMsG2
=zpCV
-----END PGP SIGNATURE-----