If you're asking which I prefer for a more complete browsing experience, I prefer Elinks. It has tabbed browsing, download/password managing, and tabbed navigation (handy when in a terminal). It also (partially) supports CSS 2.1, (fully) supports frames. It also (partially) supports JavaScript. Not as important, but Elinks supports more protocols than Lynx (I specifically use the Bittorrent protocol).
If you're asking which is more suitable for testing text-only browsers, Lynx is probably more popular, but Elinks is still a great choice here as well.
Lynx does a lot of the things elinks does, and does a fairly quick and clean job doing it.
I found only one options page and it is very easy to navigate. In fact, one of the things I liked best about lynx was it’s flat approach to configuration. Everything is right there, and easy to control.
That being said, lynx probably has the most configuration options at the command line of all the six listed here. Looking over the --help list, it seems like just about anything can be turned on or off … even turning things on or off.
w3m can display pictures on xterm and can handle table, cookies, authentication, and almost everything except JavaScript. Last stable release is not so old (0.5.3 in January 2011) but CVS repo is sleeping.
See also findthebest.com that compares software based on their technical data.
While testing these browsers through a proxy (using http_proxy=http://user:pwd@host:port/) I have been pleased to see that lynx requested for user and password so you can avoid putting them on http_proxy.
I use them as a rough visual metaphor for what it must be like to use a screen-reader. When I am addressing accessibility concerns I use Lynx to check the page when I don't have access to a screen-reader.
Why do I use Lynx? Because I wasn't aware of any alternatives!
我可以测试我的 HTML 是否真的能够承受用户关闭图像的较差浏览体验...我可以验证 ALT 标签是否有意义，等等。
Two reasons for using lynx:
It's a great way to see a lower-level of the HTTP transaction going on with the server (though, of course, you can do this with curl and such tools, but it's a pain to post forms in those tools :-) ).
I can test whether or not my HTML really holds up to a lesser browsing experience where users have images turned off... I can verify that the ALT tags make sense, etc.
Lynx，因为有时我想查找一些东西，但又不想陷入 GUI。 但多年来，这种情况越来越少，因为启动 X 的开销缓慢但稳定地增加，无法跟上摩尔的性能死亡行军。
此时我几乎保留了一个 GUI shell，甚至不用担心它。
——马库斯Q
Lynx, because sometimes I want to look something up without getting sucked into a GUI. But it's getting increasingly less frequent over the years, as the slowly but steadily increasing overhead of firing up X has failed to keep up with Moore's Death March of performance.
At this point I pretty much keep a GUI shell up and don't even worry about it.
发布评论
评论（7）
如果你问我更喜欢哪个以获得更完整的浏览体验，我更喜欢 Elinks。 它具有选项卡式浏览、下载/密码管理和选项卡式导航（在终端中很方便）。 它还（部分）支持 CSS 2.1，（完全）支持框架。 它还（部分）支持 JavaScript。 没那么重要，但 Elinks 支持的协议比 Lynx 更多（我特别使用 Bittorrent 协议）。
如果您询问哪个更适合测试纯文本浏览器，Lynx 可能更受欢迎，但 Elinks 仍然是一个不错的选择。
如需比较，请查看此处。
If you're asking which I prefer for a more complete browsing experience, I prefer Elinks. It has tabbed browsing, download/password managing, and tabbed navigation (handy when in a terminal). It also (partially) supports CSS 2.1, (fully) supports frames. It also (partially) supports JavaScript. Not as important, but Elinks supports more protocols than Lynx (I specifically use the Bittorrent protocol).
If you're asking which is more suitable for testing text-only browsers, Lynx is probably more popular, but Elinks is still a great choice here as well.
For comparision look here.
引用文本比较-基于文本的浏览器。本文包含六种基于文本的浏览器的评论和屏幕截图。
lynx 的屏幕截图
elinks 的屏幕截图
Quoting from A comparison of text-based browsers. This text contains reviews and screen shots of six text-based browsers.
Screen-shot of lynx
Screen-shot of elinks
这是对尼克·普雷斯塔的回答的补充。
维基百科上列出了十种基于文本的网络浏览器。 最活跃的三个是：
elinks是链接<的活动版本/strong>。 它的 Git 存储库 处于活动状态（自 2008 年 7 月以来有六个 0.12 测试版），但最后一个稳定版本是旧的（2009 年 8 月的 0.11.7)。lynx比 elinks 更活跃，并且最后一个稳定版本几乎同样旧（2010 年 6 月的 2.8.7rel.2）。 RCS/PRCS 存储库不是公开的，但您可以检查lynx-dev 邮件列表。w3m可以显示xterm 上的图片，可以处理表格、cookie、身份验证以及除 JavaScript 之外的几乎所有内容。 最后一个稳定版本 并不那么旧（2011 年 1 月的 0.5.3），但是 < a href="http://w3m.cvs.sourceforge.net/viewvc/w3m/w3m/?sortby=date" rel="nofollow noreferrer">CVS 存储库 正在休眠。另请参阅 findthebest.com 根据技术数据比较软件。
在通过代理测试这些浏览器时（使用
http_proxy=http://user:pwd@host:port/），我很高兴看到lynx< /strong> 请求用户和密码，这样您就可以避免将它们放在http_proxy上。This is a complement of Nick Presta's answer.
There are ten text-based web browsers listed on Wikipedia. The three most active are:
elinksis the active version oflinks. Its Git repo is alive (six 0.12 beta versions since July 2008) but last stable release is old (0.11.7 in August 2009).lynxis a bit more active thanelinksand last stable release is almost as old (2.8.7rel.2 in June 2010). The RCS/PRCS repository is not public but you can check activity of the lynx-dev mailing list.w3mcan display pictures on xterm and can handle table, cookies, authentication, and almost everything except JavaScript. Last stable release is not so old (0.5.3 in January 2011) but CVS repo is sleeping.See also findthebest.com that compares software based on their technical data.
While testing these browsers through a proxy (using
http_proxy=http://user:pwd@host:port/) I have been pleased to see thatlynxrequested foruserandpasswordso you can avoid putting them onhttp_proxy.我用它们作为一个粗略的视觉隐喻来描述使用屏幕阅读器的感觉。 当我解决可访问性问题时，当我无法访问屏幕阅读器时，我会使用 Lynx 检查页面。
我为什么使用 Lynx？ 因为我不知道有任何替代方案！
I use them as a rough visual metaphor for what it must be like to use a screen-reader. When I am addressing accessibility concerns I use Lynx to check the page when I don't have access to a screen-reader.
Why do I use Lynx? Because I wasn't aware of any alternatives!
CLI Web 浏览器有时仍然明显快于 GUI 浏览器。
更重要的是，它们也更不受干扰（没有图像、JavaScript、Flash 等），与 WriteRoom。
CLI web browsers are still sometimes noticeably faster than GUI browsers.
More importantly, they're also more distraction-free (no images, JavaScript, Flash, etc.), in much the same vein as apps like WriteRoom.
使用 lynx 的两个原因：
Two reasons for using lynx:
Lynx，因为有时我想查找一些东西，但又不想陷入 GUI。 但多年来，这种情况越来越少，因为启动 X 的开销缓慢但稳定地增加，无法跟上摩尔的性能死亡行军。
此时我几乎保留了一个 GUI shell，甚至不用担心它。
——马库斯Q
Lynx, because sometimes I want to look something up without getting sucked into a GUI. But it's getting increasingly less frequent over the years, as the slowly but steadily increasing overhead of firing up X has failed to keep up with Moore's Death March of performance.
At this point I pretty much keep a GUI shell up and don't even worry about it.
-- MarkusQ