[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] Missing link on

From: Axel Beckert
Subject: Re: [Lynx-dev] Missing link on
Date: Mon, 30 Oct 2017 15:30:56 +0100
User-agent: Mutt/1.5.21 (2010-09-15)


On Mon, Oct 30, 2017 at 11:41:01AM +0000, Ian Collier wrote:
> On Sat, Oct 28, 2017 at 07:47:16AM -0400, Thomas Dickey wrote:
> > On Sat, Oct 28, 2017 at 09:21:26AM +0200, Elimar Riesebieter wrote:
> > > according to
> > >
> > > there points a link in documentation to nowhere.
> > I pointed out that it's a problem with the package, not the upstream source.
> The Lynx source does not build cattoc.html unless configure was run
> with --enable-htmlized-cfg - but by default that setting is disabled, in
> which case the Lynx_users_guide.html that it produces contains a broken
> link.  I'd say that is an issue with the upstream source.

Thanks for that hint.

For privacy reasons many binary distributions don't like remote
startup pages, etc. and change them to local links. So do we by
patching lynx.cfg.

But if cattoc.html (and maybe other files) is just built with that
configure option (which we currently don't use), it's understandable
if instead a link to the upstream website is used.

So I checked where this link comes from in the (unpatched and unbuilt)
2.8.9dev16 sources:

  $ git grep breakout
  lynx.cfg:# is available at

The URL argued about in the bug report is

So this URL indeed is part of the unmodified upstream sources. shows
quite some files, but not cattoc.html. But it lists
and that also contains those links "by category" and "by alphabet".
But it's even worse there: They point to those two URLs where the
hostname no more exists:

This probably comes from the fact that this is not from a development
release but an rather old stable release. But doesn't exist. So I
went to and clicked on
"Online Documentation" in the left menu
( But I just got
"Forbidden — You don't have permission to access /lynx_help/ on this

Thomas: So for me it looks as if Elimar and Ian are right: This looks
like broken literal links in the upstream code and the included
prebuilt documentation as well as in the online documentation. It
would be nice if you could have a closer look at these issues. Thanks
in advance!

                Kind regards, Axel
/~\  Plain Text Ribbon Campaign                   | Axel Beckert
\ /  Say No to HTML in E-Mail and News            | address@hidden  (Mail)
 X   See | address@hidden (Mail+Jabber)
/ \  I love long mails: | (Web)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]