From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/doco] Document set/show print array-indexes
Date: Tue, 27 Sep 2005 18:57:00 -0000 [thread overview]
Message-ID: <ull1iibo4.fsf@gnu.org> (raw)
In-Reply-To: <20050927040935.GA25156@adacore.com> (message from Joel Brobecker on Mon, 26 Sep 2005 21:09:35 -0700)
> Date: Mon, 26 Sep 2005 21:09:35 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sources.redhat.com
>
> OK, I also did a "make info", just to double-check, no error as well.
Thanks.
> Note that the other commands in the same section as also lacking
> this @kindex. I can add it for you if you like (separate patch, though).
Sorry, I should have checked my memory before asking for a @kindex. I
now recall that I decided to have only one @kindex entry for all of
the "set print ..." family, and such an entry is already near the
beginning of this section.
So please don't add a @kindex entry for this new command. Sorry for
the trouble.
> <DT><CODE>set print array-indexes</CODE>
> <DD><DT><CODE>set print array-indexes on</CODE>
>
> <DD><A NAME="IDX388"></A>
> <A NAME="IDX389"></A>
> Print the index of each element when displaying arrays. May be more
> convenient to locate a given element in the array or quickly find the
> index of a given element in that printed array. The default is off.
> <P>
>
> I think the NAME tag should be just before the two <CODE> sections.
> What do you think?
Yes, you are right.
> 2005-09-26 Joel Brobecker <brobecker@adacore.com>
>
> * gdb.texinfo (Print Settings): Add documentation for set/show
> print array-indexes.
>
> Tested by building the HTML documentation and checking the result.
> Info documentation also built without any error.
Fine with me, after you remove the extra @kindex.
Thanks.
next prev parent reply other threads:[~2005-09-27 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 23:08 Joel Brobecker
2005-09-27 3:42 ` Eli Zaretskii
2005-09-27 4:10 ` Joel Brobecker
2005-09-27 18:57 ` Eli Zaretskii [this message]
2005-10-03 22:33 ` Joel Brobecker
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=ull1iibo4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--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