From: Paul Eggert <eggert@cs.ucla.edu>
To: Gavin Smith <gavinsmith0123@gmail.com>
Cc: 23611@debbugs.gnu.org, Gnulib bugs <bug-gnulib@gnu.org>,
Texinfo <bug-texinfo@gnu.org>
Subject: bug#23611: texinfo.tex 2016-05-07.20: "Tex capacity exceeded" with Emacs manuals
Date: Thu, 26 May 2016 14:17:20 -0700 [thread overview]
Message-ID: <fa2244cb-667a-bd8d-816d-f2fce6765960__14613.9296274216$1464297507$gmane$org@cs.ucla.edu> (raw)
In-Reply-To: <CAKPWYQ0p1Q9W486i0_OqTeg+EvdG6jb1EP7sVY0BsDg=m1ZETg@mail.gmail.com>
On 05/26/2016 11:41 AM, Gavin Smith wrote:
> OK, I got the same problem with the files you sent. I've committed and
> uploaded a new version that reverses the change, so @value is expanded
> at the time of writing again. Undefined @value's, when used in index
> entries, should not cause failures, either. It's quite possible that
> there is some combination that breaks, but it seems to work better for
> the files I tried.
Thanks, I verified that the new texinfo.tex works for GNU Emacs master
'make pdf', and installed it there.
next prev parent reply other threads:[~2016-05-26 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0d08fcc5-2a84-a0f1-fdf8-6832a41d21e4@cs.ucla.edu>
2016-05-26 15:20 ` bug#23611: texinfo.tex 2016-05-07.20: "Tex capacity exceeded" with Emacs manuals Gavin Smith
2016-05-26 15:48 ` Paul Eggert
[not found] ` <c92fc9c8-d0bb-3cd6-fab2-200829d9e5ac@cs.ucla.edu>
2016-05-26 18:41 ` Gavin Smith
[not found] ` <CAKPWYQ0p1Q9W486i0_OqTeg+EvdG6jb1EP7sVY0BsDg=m1ZETg@mail.gmail.com>
2016-05-26 21:17 ` Paul Eggert [this message]
2016-05-24 17:38 bug#23611: generating pdf manuals fails with TeX capacity exceeded Glenn Morris
2016-05-25 18:08 ` bug#23611: texinfo.tex 2016-05-07.20: "Tex capacity exceeded" with Emacs manuals Paul Eggert
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='fa2244cb-667a-bd8d-816d-f2fce6765960__14613.9296274216$1464297507$gmane$org@cs.ucla.edu' \
--to=eggert@cs.ucla.edu \
--cc=23611@debbugs.gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=bug-texinfo@gnu.org \
--cc=gavinsmith0123@gmail.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/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).