From: Eli Zaretskii <eliz@gnu.org>
To: "Roland Winkler" <winkler@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: texinfo-master-menu and emacs.texi
Date: Wed, 07 Dec 2011 08:19:27 -0500 [thread overview]
Message-ID: <E1RYHPD-0000vm-PC@fencepost.gnu.org> (raw)
In-Reply-To: <20191.12232.556454.551166@gargle.gargle.HOWL> (winkler@gnu.org)
> Date: Wed, 7 Dec 2011 03:20:08 -0600
> From: "Roland Winkler" <winkler@gnu.org>
>
> 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?
It would help if you'd show the error messages from the "unhappy"
makeinfo. As things are, I need to guess, and my guess is that
texinfo-master-menu does not support multi-file manuals. It only
works on a single buffer. At least I don't see in its code any hints
that it does have the ability to gather all the multiple files which
constitute the ELisp manual, using the @include directives or some
such.
My advice is to use texinfo-update-node and texinfo-make-menu on
individual nodes or groups of nodes as you go; that's what I do.
Unless your manual is on a single large file, in which case I expect
texinfo-master-menu to just work.
> Or is there a more sophisticated way of updating nodes in an
> automated fashion that works even for something like emacs.texi?
What I advise above is AFAIK the "more sophisticated way".
next prev parent reply other threads:[~2011-12-07 13:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 9:20 texinfo-master-menu and emacs.texi Roland Winkler
2011-12-07 9:57 ` Leo
2011-12-07 14:30 ` Roland Winkler
2011-12-07 13:19 ` Eli Zaretskii [this message]
2011-12-07 14:08 ` Roland Winkler
2011-12-08 6:46 ` Eli Zaretskii
2011-12-08 19:04 ` Roland Winkler
2011-12-10 11:01 ` Eli Zaretskii
2011-12-07 17:57 ` Glenn Morris
2011-12-07 19:26 ` Roland Winkler
2011-12-07 20:43 ` bug#2975: " Stefan Monnier
2011-12-07 21:19 ` Roland Winkler
2011-12-08 6:17 ` Eli Zaretskii
2011-12-08 10:38 ` Štěpán Němec
2011-12-08 12:20 ` Eli Zaretskii
2011-12-08 14:46 ` Stefan Monnier
2011-12-10 11:00 ` Eli Zaretskii
2011-12-08 18:52 ` Roland Winkler
2011-12-08 18:55 ` Roland Winkler
2011-12-08 19:06 ` Štěpán Němec
2011-12-08 19:37 ` Eli Zaretskii
2011-12-08 19:59 ` Štěpán Němec
2011-12-08 20:54 ` Roland Winkler
2011-12-09 7:28 ` Eli Zaretskii
2011-12-09 7:48 ` Roland Winkler
2011-12-10 0:17 ` Karl Berry
2011-12-10 10:57 ` Eli Zaretskii
2011-12-09 7:30 ` Eli Zaretskii
2011-12-08 19:33 ` Eli Zaretskii
2011-12-07 22:08 ` Roland Winkler
2011-12-07 22:13 ` Karl Berry
2011-12-10 12:42 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2009-04-12 21:33 bug#2975: `texinfo-master-menu' doesn't work Alan Mackenzie
2011-12-10 12:40 ` Eli Zaretskii
[not found] ` <837h24mwfs.fsf@gnu.org>
[not found] ` <20111211173859.GA2755@acm.acm>
2011-12-11 18:18 ` Eli Zaretskii
2011-12-12 12:25 ` Alan Mackenzie
2011-12-12 13:02 ` 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=E1RYHPD-0000vm-PC@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=winkler@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.