unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Greg Hogan <code@greghogan.com>
Cc: 55290-done@debbugs.gnu.org
Subject: bug#55290: Broken link to Geiser User Manual
Date: Thu, 16 Jun 2022 11:19:33 -0400	[thread overview]
Message-ID: <8735g4d4ai.fsf@gmail.com> (raw)
In-Reply-To: <87a6alinbe.fsf@gmail.com> (Maxim Cournoyer's message of "Thu, 09 Jun 2022 16:39:17 -0400")

Hi,

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> Hello Greg,
>
> Greg Hogan <code@greghogan.com> writes:
>
>> At [1] the link in "see Introduction in Geiser User Manual" points to [2]
>> but should link to [3].
>>
>> [1] https://guix.gnu.org/manual/en/html_node/The-Perfect-Setup.html
>> [2] http://geiser.nongnu.org/Introduction.html#Introduction
>> [3] https://geiser.nongnu.org/geiser_1.html#Introduction
>
> Thanks for reporting this; as Ludovic hinted on #guix, this appears to
> be a discrepancy between the file layout produced by makeinfo (used by
> Guix) vs texi2html (used by Geiser).  This problem is briefly mentioned
> in info "(texinfo)HTML Xref Mismatch".
>
> It seems 'makeinfo' should be preferred these days, since it's now
> become enough configurable and appears more actively maintained.  I've
> sent a patch to Geiser to do the switch, if they accept it this problem
> should be resolved [0].
>
> [0]  https://gitlab.com/emacs-geiser/geiser/-/merge_requests/8
>
> To be followed.

Fixed.  The Geiser documentation is now generated via 'makeinfo' rather
than 'texi2html'.

Thanks for the report!

Closing.

Maxim




      reply	other threads:[~2022-06-16 15:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 18:28 bug#55290: Broken link to Geiser User Manual Greg Hogan
2022-06-09 20:39 ` Maxim Cournoyer
2022-06-16 15:19   ` Maxim Cournoyer [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=8735g4d4ai.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=55290-done@debbugs.gnu.org \
    --cc=code@greghogan.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.
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).