-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday, August 29 at 10:50 AM, quoth Gary Johnson:
>> In html email, w3m (my usual inline html renderer) doesn't spit out
>> all the links in convenient fashion at the bottom, like elinks
>> does, and what links there are are often wrapped to the terminal
>> width. How does w3m handle that?
>
> It's true that w3m sometimes seems to break URLs at the ends of
> lines. I don't know why that is or whether the break is created by
> w3m or is in the original message. I doesn't happen often enough
> for me to have looked into it.
>
> I'm not sure I understand the issue with links at the bottom.
My point is that when, in the html, they have something like this:
Click <a href="http://example.com";>here</a>!
w3m will render that (as part of the pipe_decode process) into:
Click here!
pipe_decode uses w3m to *decode* the email before piping it to
whatever you told it to pipe to; so piping an html message to w3m with
pipe_decode set is feeding w3m its own output (read: mostly useless
for extracting links).
> o As an HTML-to-plain-text converter ahead of mutt's built-in
> pager. W3m renders the HTML as it would be seen in a browser, so
> the URLs of links are often not rendered. It doesn't really matter,
> though, since links can't followed from mutt's pager anyway. To
> follow the links in such messages, I open the HTML part of the
> message from mutt's attachment menu which runs w3m as a browser.
That's very different from what you were suggesting before. It's a few
extra steps, too...
~Kyle
- --
Liberty is the only thing you cannot have unless you are willing to
give it to others.
-- William Allen White
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFG1bT7BkIOoMqOI14RAs4QAJ9u8tSaYpQLKusdLWedXDeXkByxUACePTAt
W7pCW8zAXFCiWJyLUHtkZ/M=
=Xf1a
-----END PGP SIGNATURE-----
