Re: w3m -> standard, lynx -> optional
James Troup wrote:
As the lynx maintainer, I've demoted lynx to optional and, with the
permission of the w3m maintainer, promoted w3m to standard (and some
library packages it depends on).
Much as I love and use lynx myself, I think it's past time a text-mode
browser with better table support is made the default. (I'm assuming
this will be relatively uncontroversial, but if I'm wrong, this can
always be undone.)
I agree, that lynx is somehow past thing, and is not really friendly to
the end-user. But why w3m, and not e.g. links (eLinks acctually)? What
really important advantages it has against links? As I noticed, w3m
can't render page while downloading, and user must wait to finish, if he
wants to see the page.
One man can make a difference
-- Wilton Knight, Knight of the Phoenix (Knight Rider)