From: "Roland Winkler" <winkler@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: texinfo-master-menu and emacs.texi
Date: Thu, 8 Dec 2011 13:04:36 -0600 [thread overview]
Message-ID: <20193.2628.875570.255269@gargle.gargle.HOWL> (raw)
In-Reply-To: <E1RYXkH-0001ZG-5P@fencepost.gnu.org>
On Thu Dec 8 2011 Eli Zaretskii wrote:
> For manuals spread across several files, you need the following
> procedure:
>
> . In each individual file, run texinfo-update-node and
> texinfo-make-menu as necessary (i.e., only in those nodes which you
> modified or created anew)
>
> . After doing the above for all the constituent files, including the
> "outer" file (the main one, which includes the other ones), invoke
> "C-u M-x texinfo-multiple-files-update RET", to update the master
> menu in the "outer" file. (You will see in emacs.texi some
> comments that are evidence of this latter command being used on the
> Emacs manuals.) Please read carefully the doc string of
> texinfo-multiple-files-update and its documentation in the Texinfo
> manual, before you invoke it, to make sure you understand what it
> will do.
>
> Let me know if the above 2-step procedure does what you want.
Thanks a lot for the detailed recipe. Up to now, the texinfo manual
I want to write is really not much more than gpl.texi and
doclicense.texi. I started this thread because it was not quite
clear to me how things are supposed to work from a technical
perspective. Anyway, I need the content, too, for which I'd love
yet more if there was a single emacs command taking care of it...
So from that perspective I will need a little while before I
can report in more detail about my success or failure with this
2-step procedure.
Thanks again,
Roland
next prev parent reply other threads:[~2011-12-08 19:04 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
2011-12-07 14:08 ` Roland Winkler
2011-12-08 6:46 ` Eli Zaretskii
2011-12-08 19:04 ` Roland Winkler [this message]
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=20193.2628.875570.255269@gargle.gargle.HOWL \
--to=winkler@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.