On 2007-08-29, Kyle Wheeler <[EMAIL PROTECTED]> wrote: > On Wednesday, August 29 at 09:15 AM, quoth Gary Johnson: > >I use w3m instead of urlview for the Ctrl-B command. > > > > macro index \cB ": unset wait_key; set pipe_decode\n|w3m\n: set wait_key; > > unset pipe_decode\n" "call w3m to extract URLs out of a message" > > macro pager \cB ": unset wait_key; set pipe_decode\n|w3m\n: set wait_key; > > unset pipe_decode\n" "call w3m to extract URLs out of a message" > > > >The : command within w3m turns all URL-looking strings in the text > >into links. W3m allows you to configure as many as three external > >browsers that can be used instead of w3m itself to view the current > >page (M, 2M or 3M) or follow the current link (<Esc>M, 2<Esc>M or > >3<Esc>M). > > Interesting... why do you set pipe_decode first?
To get rid of quoted-printable or base-64 encoding. > 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. I use w3m with mutt in several ways. o As a replacement for urlview as described above. In that case, the original message is usually plain text and w3m highlights the links in their original location in the message. Personally, I like that better than having all the links at the bottom. 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. o As a pager for plain text messages that often contain URLs. Some newsletters I subscribe to contain short summaries of articles each followed by the URL of the full article. I use message-hooks to identify these messages and to set 'pager' to "w3m" or to some script that combines a filter with w3m. Again I find it more convenient to have the URLs presented as links in their original locations in the message rather than grouped at the bottom. Regards, Gary
