From: Stepan Kasal <kasal@ucw.cz>
Cc: epameinondas@gmx.de
Subject: Re: A new online publishing tool for Texinfo documents.
Date: Sun, 23 Nov 2003 13:33:09 +0100 [thread overview]
Message-ID: <20031123123309.GB9857@matsrv.math.cas.cz> (raw)
In-Reply-To: <20031123092844.GA808@fencepost>
Hi,
On Sun, Nov 23, 2003 at 04:28:44AM -0500, Miles Bader wrote:
> On Sun, Nov 23, 2003 at 10:16:45AM +0100, Stepan Kasal wrote:
> > But unless you find a reason to use elinks, start with the true links,
> > as you mentioned above.
>
> AFAIK, neither the version cited here, nor elinks, is the `true' links --
> that apparently ceased development quite a while ago, and both the above are
> forks of it.
I know the authors a bit, though I've never met them in person.
clock is the login name of Petr Kulhavy, one of the principle authors of links.
So I think the URL mentioned is ``the one true links.''
But it's not important which one will be used.
I beleive many improvements migrate both directions.
> [I say this because elinks also seems to have made many improvements, so it's
> not clear whether one or the other is to be preferred; what debian packages
> is elinks.]
And it seems to have some problems. When I go to a complex page, eg. mailman
page of holded messages, then uparrow won't get me to the top, it goes in
a weird cycle.
Though the configuration language has improved, I had problems to find the
documentation for it.
Red Hat also packages elinks, I'm actually currently using elinks, not links.
Stepan
_______________________________________________
Texinfo home page: http://www.gnu.org/software/texinfo/
texinfo-pretest@texinfo.org
http://ff0.org/mailman/listinfo/texinfo-pretest
next prev parent reply other threads:[~2003-11-23 12:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200311222102.hAML20T05380@f7.net>
2003-11-23 9:16 ` A new online publishing tool for Texinfo documents Stepan Kasal
2003-11-23 9:28 ` Miles Bader
2003-11-23 12:33 ` Stepan Kasal [this message]
2003-11-23 21:19 ` Miles Bader
2003-11-24 8:57 ` Stepan Kasal
2003-11-25 13:58 Karl Berry
-- strict thread matches above, loose matches on Subject: below --
2003-11-22 21:18 Karl Berry
2003-11-22 21:37 ` Nic Ferrier
2003-11-24 7:57 ` Juri Linkov
2003-11-24 9:11 ` Nic Ferrier
2003-11-25 4:27 ` Richard Stallman
2003-11-25 7:52 ` Juri Linkov
2003-11-25 11:21 ` Kim F. Storm
2003-11-24 14:10 ` Karl Berry
2003-11-25 21:45 ` Juri Linkov
2003-11-24 16:22 ` Richard Stallman
2003-11-24 16:39 ` Nic Ferrier
2003-11-22 20:50 Nic Ferrier
2003-11-23 16:34 ` Richard Stallman
2003-11-23 16:56 ` Nic Ferrier
2003-11-25 18:36 ` Kevin Rodgers
2003-11-25 20:05 ` Nic Ferrier
2003-11-25 22:38 ` Kim F. Storm
2003-11-26 0:21 ` Robert J. Chassell
2003-11-26 18:37 ` Kevin Rodgers
2003-11-26 21:36 ` Robert J. Chassell
2003-12-02 18:54 ` Kevin Rodgers
2003-12-02 21:56 ` Robert J. Chassell
2003-12-03 0:42 ` Kevin Rodgers
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031123123309.GB9857@matsrv.math.cas.cz \
--to=kasal@ucw.cz \
--cc=epameinondas@gmx.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).