From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: winkler@gnu.org, stepnem@gmail.com, 2975@debbugs.gnu.org,
karl@freefriends.org
Subject: bug#2975: texinfo-master-menu and emacs.texi
Date: Sat, 10 Dec 2011 13:00:11 +0200 [thread overview]
Message-ID: <83aa70n138.fsf@gnu.org> (raw)
In-Reply-To: <jwv8vmnw2gu.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: Štěpán Němec <stepnem@gmail.com>,
> 2975@debbugs.gnu.org, winkler@gnu.org,
> Karl Berry
> <karl@freefriends.org>
> Date: Thu, 08 Dec 2011 09:46:49 -0500
>
> Eli writes:
> > The simplest fix would be to remove the updating of the @node lines.
> > Would anyone object? Karl?
>
> That would be great.
I made it extremely optional instead: only "C-u N" where N is a number
would cause @node lines to be updated with next/prev/up pointers.
> Eli writes:
> > I guess I'm saying that the importance of these commands in the
> > context of maintaining Emacs documentation is somewhat exaggerated in
> > this thread, to say the least ;-)
>
> IIUC the OP is not directly interested in maintaining Emacs
> documentation but rather is trying to write a manual for another project
> (BBDB, which happens to be an Emacs package).
He was asking about the effects of invoking these commands on
emacs.texi.
> Eli writes:
> > Here's what I see there:
> > . texinfo-master-menu indeed does not support multiple-file manuals,
> > so it removed all the menu items whose nodes are in files other
> > than emacs.texi itself
>
> A good fix here would be for texinfo-master-menu to detect the problem
> and signal a warning/error.
>
> > . texinfo-master-menu doesn't grok @iftex and @ifnottext conditionals
> > (and probably the other @if... conditionals as well), so it
> > produced bad Next and Prev pointers, because, e.g., this:
>
> If leaving Node pointers alone fixes this problem, then there's nothing
> else to do, but otherwise texinfo-master-menu should try and detect
> these problematic cases and signal an error/warning.
The detection and error signaling are left as an exercise for the
interested readers ;-)
next prev parent reply other threads:[~2011-12-10 11:00 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
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 [this message]
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=83aa70n138.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=2975@debbugs.gnu.org \
--cc=karl@freefriends.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=stepnem@gmail.com \
--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.