A few minutes ago, I wrote
> I also don't see w3m as making lynx obselete:
> * lynx is in base; w3m isn't
> * lynx doesn't load images, so malicious images (e.g., ones containing
> buffer-overflow exploits for some image library) won't affect it;
> lynx has options to support displaying inline images when run from
> an xterm
/dev/brain parity error :)
What I should have written was
I also don't see w3m as making lynx obselete:
* lynx is in base; w3m isn't
* lynx doesn't load images, so malicious images (e.g., ones containing
buffer-overflow exploits for some image library) won't affect it;
w3m has options to support displaying inline images when run from
an xterm
--
-- "Jonathan Thornburg [remove -animal to reply]"
<jth...@astro.indiana-zebra.edu>
Dept of Astronomy, Indiana University, Bloomington, Indiana, USA
"C++ is to programming as sex is to reproduction. Better ways might
technically exist but they're not nearly as much fun." -- Nikolai Irgens
