From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tomasn@posteo.net, 24624@debbugs.gnu.org
Subject: bug#24624: 24.4; Faulty info link -> definition of nth
Date: Fri, 07 Oct 2016 09:09:57 +0200 [thread overview]
Message-ID: <57F74A45.4060307@gmx.at> (raw)
In-Reply-To: <83k2dljpuo.fsf@gnu.org>
> It's not up to Emacs, it's up to Texinfo developers. We here had no
> say in this matter. Once Texinfo switched to makeinfo the Perl
> script, it got much slower. (If you build Texinfo locally, you can
> build it with Perl extensions in C, which makes it about 40% faster,
> but that's still 10 times slower than the C version.)
It already became much slower before that switch. No wonder it takes me
years to write documentation like that on side windows ;-)
>> > Yes, we changed the code in Emacs's Info reader to be compatible with
>> > how the new Texinfo calculates positions in tag tables. There was no
>> > other reasonable solution.
>>
>> It would have been good to read something about this in NEWS or
>> somewhere else.
>
> You mean, in Texinfo NEWS?
Emacs NEWS should have said that "we changed the code in Emacs's Info
reader to be compatible with how the new Texinfo calculates positions in
tag tables". But since I am probably the only other person to edit
texinfo files on Windows, a PM might have been sufficient.
martin
next prev parent reply other threads:[~2016-10-07 7:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 20:01 bug#24624: 24.4; Faulty info link -> definition of nth Tomas Nordin
2016-10-06 6:48 ` Eli Zaretskii
2016-10-06 8:50 ` martin rudalics
2016-10-06 8:59 ` Eli Zaretskii
2016-10-06 16:27 ` martin rudalics
2016-10-06 18:26 ` Eli Zaretskii
2016-10-07 7:09 ` martin rudalics [this message]
[not found] ` <87twcpvlcr.fsf@flaptop.tomnor.org>
2016-10-06 10:45 ` Eli Zaretskii
2016-10-06 21:10 ` Tomas Nordin
2016-10-07 7:33 ` Eli Zaretskii
[not found] ` <87wphiu052.fsf@flaptop.tomnor.org>
2016-10-08 19:49 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57F74A45.4060307@gmx.at \
--to=rudalics@gmx.at \
--cc=24624@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tomasn@posteo.net \
/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/emacs.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).