From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: control@debbugs.gnu.org, Greg Hogan <code@greghogan.com>,
66703@debbugs.gnu.org
Subject: bug#66703: Broken link to Debbugs User Guide
Date: Tue, 31 Oct 2023 11:19:04 -0400 [thread overview]
Message-ID: <87ttq6rf9z.fsf@gmail.com> (raw)
In-Reply-To: <878r7o23d6.fsf@protonmail.com> (John Kehayias's message of "Fri, 27 Oct 2023 02:42:10 +0000")
Hi John,
John Kehayias <john.kehayias@protonmail.com> writes:
> merge 66703 58415
> thanks
>
> On Mon, Oct 23, 2023 at 10:39 PM, Maxim Cournoyer wrote:
>
>> Hi Greg,
>>
>> Greg Hogan <code@greghogan.com> writes:
>>
>>> The page https://guix.gnu.org/devel/manual/en/html_node/Debbugs-User-Interfaces.html
>>> has a broken link "Debbugs User Guide" to the page
>>> https://guix.gnu.org/devel/manual/en/debbugs-ug/index.html#Top.
>>
>> There doesn't seem to be an online HTML version of this manual, so the
>> bug doesn't appear actionable.
>>
>> It works when using 'info', provided the 'emacs-debbugs' package is
>> installed.
>
> I noticed the broken html link before but never tracked down the correct
> link to patch it. But just now a search gave me
> <https://elpa.gnu.org/packages/doc/debbugs-ug.html> which looks helpful?
This doesn't look like an 'official' doc to me, but if we'd like to use
it, we'd have to tune the doc/htmlxref.cnf file content. Would you like
to give it a try?
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-10-31 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 14:51 bug#66703: Broken link to Debbugs User Guide Greg Hogan
2023-10-24 2:39 ` Maxim Cournoyer
2023-10-27 2:42 ` John Kehayias via Bug reports for GNU Guix
2023-10-31 15:19 ` Maxim Cournoyer [this message]
2024-06-15 12:01 ` bug#66703: [PATCH] doc: Remove 'Debbugs User Guide' broken links Vincent Legoll
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=87ttq6rf9z.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=66703@debbugs.gnu.org \
--cc=code@greghogan.com \
--cc=control@debbugs.gnu.org \
--cc=john.kehayias@protonmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.