From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: Eli Zaretskii <eliz@is.elta.co.il>, ac131313@cygnus.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] document Cygwin native specific commands
Date: Wed, 20 Feb 2002 02:20:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20020220111422.014f0140@ics.u-strasbg.fr> (raw)
In-Reply-To: <563-Tue19Feb2002192641+0200-eliz@is.elta.co.il>
At 18:26 19/02/2002 , Eli Zaretskii a écrit:
> > Date: Tue, 19 Feb 2002 11:37:35 -0500
> > From: Andrew Cagney <ac131313@cygnus.com>
> >
> > Hmm. Given a dump of all of GDB's commands, should there be a kindex
> > for each?
>
>Yes, each command described in the manual should be indexed. That
>way, all users need to type to find the documentation of any given
>command CMD is "i CMD <RET>", once they are in an Info reader.
Sorrry, Eli, but I don't really understand what I should do here.
Thus I looked at the subsection above concerning DJGPP
specific commands, but there I find a kindex entry
for :
"info dos"
"sysinfo"
but nothing for ldt gdt idt dos subcommands....
Shouldn't there be
@kindex info dos
...
@kindex info dos sysinfo
...
@kindex info dos ldt
@kindex info dos gdt
@kindex info dos idt
?????
In my code I added a
@kindex shell
but there is a
"shell" command
and I was documenting
"set shell" Cygwin specifc command....
So
-- should I use
@kindex set shell
?
-- shouldn't in be a w32 subcommand ?
but is this possible for set/show commands ?
Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
next prev parent reply other threads:[~2002-02-20 10:20 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
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 [this message]
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=4.2.0.58.20020220111422.014f0140@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
/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