public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James Broadhead <jamesbroadhead@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Lynx, Links, or Elinks?
Date: Fri, 9 Dec 2011 14:09:31 +0000	[thread overview]
Message-ID: <CA+hid6EZAiBVE72RWfVAxbEAjt-jx0nzfyNWjXSnHm+=v-XVVA@mail.gmail.com> (raw)
In-Reply-To: <CAJTyqKMczcenzzgkOeuaiF43FZ2H-vgJ8b4jP5n38LGX0KoCoQ@mail.gmail.com>

On 9 December 2011 12:44, Mariusz Ceier <mceier@gmail.com> wrote:
> w3m,links and elinks. w3m and links as they support displaying images
> under framebuffer, and elinks for it's javascript support.
> If you don't need these features, any text browser is good for
> browsing html documentation :)

Not too long ago, I was using elinks for the same reason, but found
that sites were complaining about the amount of js support, telling me
to upgrade :-(


Afterthought: it was actually the Oracle website where I was going to
get the jdk / documentation, which has gone back to being
fetch-restricted :-(  :-(  :-(



  parent reply	other threads:[~2011-12-09 14:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 11:38 [gentoo-user] Lynx, Links, or Elinks? Pandu Poluan
2011-12-09 12:27 ` Lavender
2011-12-09 12:44 ` [gentoo-user] " Mariusz Ceier
2011-12-09 13:04   ` Willie WY Wong
2011-12-09 14:09   ` James Broadhead [this message]
2011-12-09 15:28 ` Paul Hartman
2011-12-09 19:11 ` Philip Webb
2011-12-09 20:01   ` [gentoo-user] " Hartmut Figge
2011-12-09 22:49     ` David Haller
2011-12-10 12:36 ` [gentoo-user] " luis jure
2011-12-10 23:13   ` Frank Steinmetzger
2011-12-12  9:21     ` Aljosha Papsch
     [not found] <i677I-gC-11@gated-at.bofh.it>
     [not found] ` <i67U5-1CY-5@gated-at.bofh.it>
2011-12-09 14:57   ` Indi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+hid6EZAiBVE72RWfVAxbEAjt-jx0nzfyNWjXSnHm+=v-XVVA@mail.gmail.com' \
    --to=jamesbroadhead@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox