From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Roland Winkler" Newsgroups: gmane.emacs.devel Subject: texinfo-master-menu and emacs.texi Date: Wed, 7 Dec 2011 03:20:08 -0600 Message-ID: <20191.12232.556454.551166@gargle.gargle.HOWL> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1323249620 22692 80.91.229.12 (7 Dec 2011 09:20:20 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 7 Dec 2011 09:20:20 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 07 10:20:16 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RYDfk-00073h-C9 for ged-emacs-devel@m.gmane.org; Wed, 07 Dec 2011 10:20:16 +0100 Original-Received: from localhost ([::1]:52934 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RYDfj-0000ec-Jf for ged-emacs-devel@m.gmane.org; Wed, 07 Dec 2011 04:20:15 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:54711) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RYDfg-0000eX-U0 for emacs-devel@gnu.org; Wed, 07 Dec 2011 04:20:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RYDff-0004vq-Rb for emacs-devel@gnu.org; Wed, 07 Dec 2011 04:20:12 -0500 Original-Received: from essmail.ess.niu.edu ([131.156.1.18]:46402) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RYDff-0004vc-Mm for emacs-devel@gnu.org; Wed, 07 Dec 2011 04:20:11 -0500 Original-Received: from regnitz (lukas.physics.niu.edu [131.156.85.221]) by essmail.ess.niu.edu (8.14.3/8.14.3) with ESMTP id pB79K88o021355 for ; Wed, 7 Dec 2011 03:20:09 -0600 (CST) X-Mailer: VM 8.2 trial under 24.0.90.2 (x86_64-unknown-linux-gnu) X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 131.156.1.18 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:146537 Archived-At: I am trying to write a more up-to-date info manual for BBDB. However, I am not yet familiar with the subtleties of how to set up an info manual. For a more advanced example for how this can be done I looked into emacs.texi. The texinfo manual says about "Updating Nodes and Menus" If you do not use the updating commands, you need to write menus and node pointers by hand, which is a tedious task. The emacs command texinfo-master-menu (used with a prefix arg) is supposed to do that; according to the doc string it updates all existing nodes and menus. Yet when I run this command on emacs.texi, this brings emacs.texi into a format that makes makeinfo rather unhappy. What is going on here? Is emacs.texi too advanced for emacs' texinfo mode so that nodes need to be updated by hand? Or is there a more sophisticated way of updating nodes in an automated fashion that works even for something like emacs.texi? What kind of constructs in emacs.texi go beyond the capabilities of texinfo-master-menu so that (at least in the beginning) I might want to avoid them? Any hints are appreciated. Roland