From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: GTK documentation in Emacs
Date: Fri, 10 Jan 2003 22:27:43 +0300 [thread overview]
Message-ID: <6480-Fri10Jan2003222743+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <200301091754.h09HsDDU023888@stubby.bodenonline.com> (jan.h.d@swipnet.se)
> From: "Jan D." <jan.h.d@swipnet.se>
> Date: Thu, 9 Jan 2003 17:58:06 +0100 (CET)
>
> 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
> + @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.
next prev parent reply other threads:[~2003-01-10 19:27 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 [this message]
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
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=6480-Fri10Jan2003222743+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).