From: zimoun <zimon.toutoune@gmail.com>
To: 29593@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
"Tobias Geerinckx-Rice" <me@tobias.gr>
Subject: bug#29593: Bug #29593 Hunting: Broken links in the HTML manual
Date: Thu, 21 Nov 2019 17:03:22 +0100 [thread overview]
Message-ID: <CAJ3okZ04ocfaaCVODYQMy8HXZ--pHF0TMxk42mrKEpwPbiohyw@mail.gmail.com> (raw)
In-Reply-To: <CAJ3okZ19ARFznp4QdHqecmXwJd9qYwB_AX3gtvtMuChPF8O6sg@mail.gmail.com>
Hi Tobias,
My quick tests were really quick! ;-)
These links remains broken. Do you have any patch fixing them that you
forgot to push?
Or do I invest more time to propose a patch?
Thank you in advance.
Cheers,
simon
Same with the online "manual/devel".
- Package Management[1]:
“The Emacs-Guix Reference Manual” is broken.
It points to a URI with duplicate ‘/index.html’s.
This link [1b] is still broken.
[1] https://www.gnu.org/software/guix/manual/html_node/Package-Management.html
[1b] https://guix.gnu.org/manual/en/emacs-guix/index.html#Top
Seems broken in Info too.
Related to Formatting Code [3].
Similarly points to ‘index.html/Development.html’ when it should use
only ‘Development.html’.
[3] https://www.gnu.org/software/guix/manual/html_node/Formatting-Code.html
[3b] https://guix.gnu.org/manual/en/emacs-guix/Development.html#Development
contributing.texi:
@pxref{Development,,, emacs-guix, The Emacs-Guix Reference Manual}
- Using the Offload Facility[2]:
“Converting keys” points to #Converting-keys, the target site uses
#Converting%20keys. I don't know who's right. The page still loads
so the user can navigate manually, but it would still be nice to fix.
The manual (texi entry: @pxref{Converting keys,,, lsh, LSH Manual}) points to
[2b] and the working link is [2c].
[2] https://www.gnu.org/software/guix/manual/html_node/Daemon-Offload-Setup.html
[2b] http://www.lysator.liu.se/~nisse/lsh/lsh.html#Converting-keys
[2c] http://www.lysator.liu.se/~nisse/lsh/lsh.html#Converting%20keys
How to fix it?
- Networking Services[4]:
“lsh-make-seed” and “lshd basics” also use bad anchors, so the user
has to search and scroll.
Idem as previous.
[4] https://www.gnu.org/software/guix/manual/html_node/Networking-Services.html
[4b] http://www.lysator.liu.se/~nisse/lsh/lsh.html#lsh_002dmake_002dsede
[4c] http://www.lysator.liu.se/~nisse/lsh/lsh.html#lshd%20basics
- The Perfect Setup[5]:
“Introduction in the Geiser User Manual” is a broken link.
The entry is @pxref{Introduction,,, geiser, Geiser User Manual} which works in
Info but is broken online.
[5] https://www.gnu.org/software/guix/manual/html_node/The-Perfect-Setup.html
[5b] https://guix.gnu.org/manual/en/geiser/Introduction.html#Introduction
[5c] http://nongnu.org/geiser/geiser_1.html#Introduction
- Continuous Integration[6]:
“Associations Lists in GNU Guile Reference Manual” is broken.
It points inside the Guix manual, not Guile's.
The page [6] points to [6b] which is broken.
[6] https://www.gnu.org/software/guix/manual/html_node/Continuous-Integration.html
[6b] https://www.gnu.org/software/guile/manual/html_node/Associations-Lists.html#Associations-Lists
Is the link also broken with Info?
- Mapped Devices[7]:
“Translators in The GNU Hurd Reference Manual” is broken.
It points inside the Guix manual, not The Hurd's.
Idem as previous.
[7] https://www.gnu.org/software/guix/manual/html_node/Mapped-Devices.html
[7b] https://guix.gnu.org/manual/en/hurd/Translators.html#Translators
- Documentation[8]:
“Getting Started in Info: An Introduction” is broken.
Idem.
[8] https://www.gnu.org/software/guix/manual/html_node/Documentation.html
[8b] https://guix.gnu.org/manual/en/info/Getting-Started.html#Getting-Started
prev parent reply other threads:[~2019-11-21 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 19:35 bug#29593: [web site] Broken links in the HTML manual Tobias Geerinckx-Rice
2017-12-07 21:11 ` Ludovic Courtès
2017-12-07 22:52 ` Tobias Geerinckx-Rice
2019-11-12 20:57 ` bug#29593: Bug #29593 Hunting: status? zimoun
2019-11-21 16:03 ` zimoun [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ04ocfaaCVODYQMy8HXZ--pHF0TMxk42mrKEpwPbiohyw@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=29593@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
/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/guix.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).