From: Aljosha Papsch <papsch.al@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Lynx, Links, or Elinks?
Date: Mon, 12 Dec 2011 10:21:55 +0100 [thread overview]
Message-ID: <1323681715.8874.2.camel@creek.rivers> (raw)
In-Reply-To: <20111210231318.GD5966@eisen.lan>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
Am Sonntag, den 11.12.2011, 00:13 +0100 schrieb Frank Steinmetzger:
> On Sat, Dec 10, 2011 at 10:36:32AM -0200, luis jure wrote:
>
> > >As the subject says: Which text browser do you recommend?
> >
> > i haven't used text browsers for some time now, but i definitely
> prefered
> > links over lynx. if i were you, i would try both. for me the links
> > interface was much better, although lynx seems to be better known or
> more
> > widely used.
>
> I like elinks for its tabs capability and easy configurability through
> its GUI
> (the latter isn’t a killer feature in console land, but it makes it
> easy for
> example to find every keyboard-assignable feature it has).
I like elinks and lynx for their proxy support. lynx simply uses *_proxy
environment variables, elinks must be configured in it's menu. links
doesn't support https over proxy.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-12-12 9:21 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
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 [this message]
[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=1323681715.8874.2.camel@creek.rivers \
--to=papsch.al@googlemail.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