unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 23611@debbugs.gnu.org
Subject: bug#23611: generating pdf manuals fails with TeX capacity exceeded
Date: Wed, 25 May 2016 14:48:43 -0400	[thread overview]
Message-ID: <65eg8q3rec.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <5f622904-aaff-fb27-d342-70ec6189ad3f@cs.ucla.edu> (Paul Eggert's message of "Wed, 25 May 2016 10:45:21 -0700")

Paul Eggert wrote:

> As I understand it, changes to texinfo.tex are fair game since it's
> just documentation.

Surely it is obvious that such a change is not a "documentation change".
It is a (totally opaque, for me at least) change to the mechanism that
generates documentation, which isn't the same thing at all.

>  At this point, though, it may be wise to stop updating texinfo.tex
> from Gnulib unless the update fixes a known bug in the Emacs
> documentation and does not cause problems like this one.

s/this point.*wise to/During pretesting,/





  reply	other threads:[~2016-05-25 18:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 17:38 bug#23611: generating pdf manuals fails with TeX capacity exceeded Glenn Morris
2016-05-25 16:53 ` Eli Zaretskii
2016-05-25 17:45 ` Paul Eggert
2016-05-25 18:48   ` Glenn Morris [this message]
2016-05-25 22:51     ` Paul Eggert
2016-05-25 19:30   ` Eli Zaretskii
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=65eg8q3rec.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=23611@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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).