From: Steinar Bang <sb@dod.no>
Cc: Hrvoje Niksic <hniksic@arsdigita.com>
Subject: Re: Using `links' to process HTML
Date: Sun, 17 Feb 2002 18:36:13 +0100 [thread overview]
Message-ID: <87664wf1te.fsf@bang.priv.no> (raw)
In-Reply-To: <sxsy9hth4t4.fsf@florida.arsdigita.de>
>>>>> Hrvoje Niksic <hniksic@arsdigita.com>:
> Matthieu Moy <Matthieu.Moy@imag.fr> writes:
>> What is the difference (except the use of lynx instead of links) ?
> * Links is so much cooler than lynx. For one, it handles HTML
> tables correctly.
Links (0.96.20011222 on debian testing) doesn't seem to do HTTP Basic
auth, though.
next prev parent reply other threads:[~2002-02-17 17:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 7:08 Hrvoje Niksic
2002-02-15 16:24 ` Nevin Kapur
2002-02-16 14:09 ` Matthieu Moy
2002-02-16 14:36 ` Hrvoje Niksic
2002-02-17 17:36 ` Steinar Bang [this message]
2002-02-16 15:33 ` Nevin Kapur
2002-02-16 16:16 ` Kai Großjohann
2002-02-16 18:02 ` Nuutti Kotivuori
2002-02-21 19:37 ` Paul Jarc
2002-02-21 19:37 ` Paul Jarc
2002-02-18 0:44 ` ShengHuo ZHU
2002-02-18 8:55 ` Matthieu Moy
2002-02-18 15:34 ` ShengHuo ZHU
2002-02-18 15:37 ` Steve Youngs
2002-02-18 18:48 ` ShengHuo ZHU
2002-02-18 23:14 ` Steve Youngs
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=87664wf1te.fsf@bang.priv.no \
--to=sb@dod.no \
--cc=hniksic@arsdigita.com \
/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;
as well as URLs for NNTP newsgroup(s).