From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] document Cygwin native specific commands
Date: Wed, 20 Feb 2002 04:16:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20020220124517.024e25f0@ics.u-strasbg.fr> (raw)
In-Reply-To: <Pine.SUN.3.91.1020220131109.24579B-100000@is>
At 12:18 20/02/2002 , Eli Zaretskii a écrit:
>On Wed, 20 Feb 2002, Pierre Muller wrote:
>
> > 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
> > ?????
>
>I didn't include the subcommands on purpose. The reason is that it is
>not useful to have several index entries that all begin with the same
>string and point to the same page in the manual. That is why I only
>indexed "info dos".
>
>So I guess my assertion about ``every command'' should have been
>qualified by this exception. Sorry for confusion.
But why did you kindex sysinfo and not the other ones?
> > So
> > -- should I use
> > @kindex set shell
> > ?
>
>Yes. That is how all "set ..." commands are indexed in the manual,
>AFAICS.
OK!
> > -- shouldn't in be a w32 subcommand ?
>
>Sorry, I don't understand: the command is "set shell", not "set w32 shell",
>right? If so, you should have "@kindex set shell".
No I was asking if this "set shell " command
should not be replaced by a "set w32 shell" command.
But I am not sure how this could be done...
because add_show_from_set and add_set_cmd are
special functions.
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 12:16 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
2002-02-20 3:19 ` Eli Zaretskii
2002-02-20 4:16 ` Pierre Muller [this message]
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.20020220124517.024e25f0@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--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