From: Juri Linkov <juri@jurta.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ludo@gnu.org, 21055@debbugs.gnu.org
Subject: bug#21055: Info reader fails to follow xrefs to anchors
Date: Wed, 15 Jul 2015 02:16:32 +0300 [thread overview]
Message-ID: <874ml6s52n.fsf@mail.linkov.net> (raw)
In-Reply-To: <83y4ii7pmz.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 14 Jul 2015 17:57:56 +0300")
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
> Juri, do you see any flaws in the above description? I couldn't
> reproduce the problem reported in bug #14125, so I'm not sure why the
> fix you installed was even needed, or where my reasoning is wrong. I
> tried both Emacs 24.3 (for which the bug was filed) and later
> versions, and they all work correctly with the Info file produced from
> the Texinfo source attached to that bug report, no matter if I produce
> the Info file with makeinfo 4.13 or makeinfo 5.1 or 6.0. So I'm
> unsure what problems you saw with the original code in
> Info-read-subfile. Could you describe those problems in more detail
> than you did in the bug discussions?
I'm attaching here all the files that I used to fix bug#14125,
so you could compare the output of different makeinfo versions
and see the problem. The command line used to translate
Texinfo files was: makeinfo --split-size=2000 test.texi
[-- Attachment #2: bug_14125.zip --]
[-- Type: application/zip, Size: 7762 bytes --]
next prev parent reply other threads:[~2015-07-14 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87615o2l0e.fsf@gnu.org>
[not found] ` <83h9p884w2.fsf@gnu.org>
[not found] ` <87twt7x18d.fsf@gnu.org>
2015-07-14 14:57 ` bug#21055: Info reader fails to follow xrefs to anchors Eli Zaretskii
2015-07-14 23:16 ` Juri Linkov [this message]
2015-07-15 15:09 ` Eli Zaretskii
2015-07-16 22:49 ` Juri Linkov
2015-07-18 10:24 ` 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=874ml6s52n.fsf@mail.linkov.net \
--to=juri@jurta.org \
--cc=21055@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ludo@gnu.org \
/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.