Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: muller@cerbere.u-strasbg.fr
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] document Cygwin native specific commands
Date: Tue, 19 Feb 2002 05:25:00 -0000	[thread overview]
Message-ID: <4760-Tue19Feb2002152216+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <4.2.0.58.20020219102752.0248dc18@ics.u-strasbg.fr> (message from Pierre Muller on Tue, 19 Feb 2002 10:31:37 +0100)

> 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.


  reply	other threads:[~2002-02-19 13:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-19  1:32 Pierre Muller
2002-02-19  5:25 ` Eli Zaretskii [this message]
2002-02-19  8:28   ` Andrew Cagney
2002-02-19  8:37   ` Andrew Cagney
2002-02-19  9:29     ` Eli Zaretskii
2002-02-19 14:37       ` Andrew Cagney
2002-02-19 22:58         ` Eli Zaretskii
2002-02-20  2:20       ` Pierre Muller
2002-02-20  3:19         ` Eli Zaretskii
2002-02-20  4:16           ` Pierre Muller
2002-02-20  5:16             ` Eli Zaretskii
2002-02-20  7:57               ` [RFC] document cygwin " Christopher Faylor
2002-02-20  9:41                 ` Eli Zaretskii
2002-02-19  9:10   ` Christopher Faylor
2002-02-19 11:32     ` Eli Zaretskii
2002-02-20  4:18 [RFC] document Cygwin " Pierre Muller
2002-02-20  5:16 ` Eli Zaretskii
2002-02-20  7:58   ` [RFC] document cygwin " Christopher Faylor
2002-02-20  8:11     ` Pierre Muller

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=4760-Tue19Feb2002152216+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=muller@cerbere.u-strasbg.fr \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox