From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: GTK documentation in Emacs
Date: Sat, 11 Jan 2003 17:48:06 +0300 [thread overview]
Message-ID: <2427-Sat11Jan2003174805+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <200301111157.h0BBv9DU032103@stubby.bodenonline.com> (jan.h.d@swipnet.se)
> From: "Jan D." <jan.h.d@swipnet.se>
> Date: Sat, 11 Jan 2003 12:01:21 +0100 (MET)
> Cc: emacs-devel@gnu.org
>
> >
> > > From: "Jan D." <jan.h.d@swipnet.se>
> > > Date: Sat, 11 Jan 2003 09:29:18 +0100 (CET)
> > >
> > > When I use "@node Foo" only I get this:
> > > ./xresources.texi:585: `GTK widget paths' has no Up field.
> > > ./xresources.texi:636: `GTK names in Emacs' has no Up field.
> > > ./xresources.texi:720: `GTK styles' has no Up field.
> > > makeinfo: Removing output file `../info/emacs' due to errors; use --force to preserve.
> >
> > This happens because your top-level GTK section has the @appendixsec
> > directive in it, but all the other sections, which are subsections of
> > the top-level section, always use @appendixsec. You should instead
> > use @appendixsubsec in the 3 subsections; then the problem will go
> > away. (Sorry I didn't mention this restriction in my message.)
>
> I just figured this out :-)
>
> > As the node "makeinfo Pointer Creation" in the Texinfo manual
> > explains, makeinfo uses the sectioning commands to deduce the
> > hierarchical structure of the document. So you must use the
> > sectioning commands, and you must mark each chapter and section
> > correctly with sectioning commands, for the automatic pointer creation
> > to work.
>
> This makes sense. I wish maekinfo said something about "sectioning
> structure not consistent with menu structure" or something like
> that.
I agree. I cc'ed Karl Berry, who is the Texinfo maintainer, in the
hope that the error message could be improved in some future release.
next prev parent reply other threads:[~2003-01-11 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 16:58 GTK documentation in Emacs Jan D.
2003-01-09 20:54 ` Jan D.
2003-01-10 3:27 ` Miles Bader
2003-01-10 17:20 ` Jan D.
2003-01-11 1:27 ` Miles Bader
2003-01-10 19:27 ` Eli Zaretskii
2003-01-10 20:45 ` Jan D.
2003-01-10 19:56 ` Eli Zaretskii
2003-01-11 8:29 ` Jan D.
2003-01-11 9:23 ` Eli Zaretskii
2003-01-11 11:01 ` Jan D.
2003-01-11 14:48 ` Eli Zaretskii [this message]
2003-01-11 9:49 ` Kai Großjohann
2003-01-11 10:57 ` Jan D.
-- strict thread matches above, loose matches on Subject: below --
2003-01-11 16:50 Karl Berry
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=2427-Sat11Jan2003174805+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--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 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).