From: Rahguzar via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 72391@debbugs.gnu.org
Subject: bug#72391: 29.4; Info cannot find anchors after Info-on-current-buffer
Date: Fri, 02 Aug 2024 11:22:30 +0200 [thread overview]
Message-ID: <87v80jffe1.fsf@zohomail.eu> (raw)
In-Reply-To: <86a5hvwi8f.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 02 Aug 2024 09:29:04 +0300")
Hi Eli,
I tested and it is fixed for me. As always, thanks a lot!
Rahguzar
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Wed, 31 Jul 2024 09:34:09 +0200
>> From: Rahguzar via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> I am trying to generate an info manual for the SageMath. In the process
>> I found that Info can't follow references to anchors atfer `M-x
>> Info-on-current-buffer`. To see, please download the manual
>> https://github.com/user-attachments/files/16425138/sage.info.gz (It is
>> 12 MB compressed so very large). Then from Emacs -Q:
>>
>> 1. Open the downloaded manual in a buffer.
>> 2. M-x Info-on-current-buffer RET
>> 3. Navigate to: (sage.info)Top > Welcome to Sage Reference Manual > User Interfaces
>> 4. Click on Command Line Interface
>>
>> This results in Info-find-node-2: No such node or anchor: ccf
>
> Thanks, should be fixed now on the master branch.
next prev parent reply other threads:[~2024-08-02 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 7:34 bug#72391: 29.4; Info cannot find anchors after Info-on-current-buffer Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-02 6:29 ` Eli Zaretskii
2024-08-02 9:22 ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-08-02 10:33 ` Eli Zaretskii
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=87v80jffe1.fsf@zohomail.eu \
--to=bug-gnu-emacs@gnu.org \
--cc=72391@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rahguzar@zohomail.eu \
/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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.