From: "Jan D." <jan.h.d@swipnet.se>
Subject: Re: GTK documentation in Emacs
Date: Fri, 10 Jan 2003 21:45:39 +0100 [thread overview]
Message-ID: <7A72D9C8-24DC-11D7-AA49-00039363E640@swipnet.se> (raw)
In-Reply-To: <6480-Fri10Jan2003222743+0200-eliz@is.elta.co.il>
>> I will shortly check in the GTK changes in to CVS, I really would like
>> some feedback on the documentation I've written
>
> Thanks! A couple of technical points:
>
>> + @node GTK resources, GTK widget paths, LessTif Resources, X Resources
>> + @appendixsec GTK resources
>> + @cindex GTK resources
>> + @cindex GTK customize
>> + @cindex GTK resource files
>
> It is not useful to have multiple index entries pointing to the same
> place and beginning with the same string. So I suggest to replace the
> 3 index entries above with this:
>
> @cindex GTK resources and customization
> @cindex resource files for GTK
Good point, I will change this.
>> + @node GTK widget paths, GTK names in Emacs, GTK resources, GTK resources
>
> 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.
Jan D.
next prev parent reply other threads:[~2003-01-10 20:45 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. [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7A72D9C8-24DC-11D7-AA49-00039363E640@swipnet.se \
--to=jan.h.d@swipnet.se \
/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.