This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] document Cygwin native specific commands
- From: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
- To: muller at cerbere dot u-strasbg dot fr
- Cc: gdb-patches at sources dot redhat dot com
- Date: Tue, 19 Feb 2002 15:22:16 +0200
- Subject: Re: [RFC] document Cygwin native specific commands
- References: <4.2.0.58.20020219102752.0248dc18@ics.u-strasbg.fr>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Tue, 19 Feb 2002 10:31:37 +0100
> From: Pierre Muller <muller@cerbere.u-strasbg.fr>
>
> I have no experience with texinfo ...
Don't worry, that's what I'm here for ;-)
> I still don't know what the difference between @kindex and @cindex is :(
The GDB manual uses @kindex to put all the GDB commands into a
separate index, while @cindex entries go into the Concept Index.
Right now, this line near the beginning of gdb.texinfo:
@syncodeindex ky cp
causes the @kindex entries to be printed together with the @cindex
entries. But it is enough to remove that line to cause them to be in
2 different indices.
So whenever you want to add an index entry for a command, please
always put it into @kindex.
> +@node Cygwin Native
> +@subsection Features for Debugging @sc{win32} PE executables
> +@cindex @sc{win32} debugging
> +@cindex native Cygwin debugging
> +@cindex Win32-specific commands
As I said earlier, I'd really prefer that you say "Windows
applications" or "native Windows debugging", instead of using
"win32".
Otherwise, this can go in, as far as I'm concerned.