From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: GTK documentation in Emacs
Date: Sat, 11 Jan 2003 09:29:18 +0100 (CET) [thread overview]
Message-ID: <200301110925.h0B9P9DU029715@stubby.bodenonline.com> (raw)
In-Reply-To: <9791-Fri10Jan2003225621+0200-eliz@is.elta.co.il> "from Eli Zaretskii at Jan 10, 2003 10:56:21 pm"
> > Date: Fri, 10 Jan 2003 21:45:39 +0100
> > From: "Jan D." <jan.h.d@swipnet.se>
> > >
> > > In general, please use just "@node Foo", without the prev/next/up
> > > links, as in "@node GTK widget paths". This makes it easier to move
> > > nodes around.
> >
> > Hmm, I had that at first and then makeinfo complained. I probably
> > did something wrong, I'll look in to this.
>
> For this to work, you need to put the nodes in the depth-first-search
> order, and you need to have a menu item in the parent node for each of
> its child nodes. makeinfo should tell what is wrong, but if you
> cannot figure out its messages, please post them and I will try to
> help.
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.
I don't know how to fix that except by adding the prev/next/up links.
Jan D.
next prev parent reply other threads:[~2003-01-11 8:29 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. [this message]
2003-01-11 9:23 ` Eli Zaretskii
2003-01-11 11:01 ` Jan D.
2003-01-11 14:48 ` Eli Zaretskii
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=200301110925.h0B9P9DU029715@stubby.bodenonline.com \
--to=jan.h.d@swipnet.se \
--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).