From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: muller@cerbere.u-strasbg.fr, gdb-patches@sources.redhat.com
Subject: Re: [RFC] document Cygwin native specific commands
Date: Tue, 19 Feb 2002 08:37:00 -0000 [thread overview]
Message-ID: <3C727F4F.5020100@cygnus.com> (raw)
In-Reply-To: <4760-Tue19Feb2002152216+0200-eliz@is.elta.co.il>
>
> 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.
Hmm. Given a dump of all of GDB's commands, should there be a kindex
for each? What about the reverse?
I think we might have just stumbled across something that is feasible
for the ARI to check.
enjoy,
Andrew
next prev parent reply other threads:[~2002-02-19 16:37 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
2002-02-19 8:28 ` Andrew Cagney
2002-02-19 8:37 ` Andrew Cagney [this message]
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=3C727F4F.5020100@cygnus.com \
--to=ac131313@cygnus.com \
--cc=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