From: Eli Zaretskii <eliz@gnu.org>
To: tromey@redhat.com
Cc: bauerman@br.ibm.com, gdb-patches@sourceware.org
Subject: Re: [rfc] python API exposing inferior's frame stack.
Date: Tue, 17 Mar 2009 22:43:00 -0000 [thread overview]
Message-ID: <uhc1rrebj.fsf@gnu.org> (raw)
In-Reply-To: <m3ljr3lv8c.fsf@fleche.redhat.com>
> Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>, gdb-patches@sourceware.org
> From: Tom Tromey <tromey@redhat.com>
> Date: Tue, 17 Mar 2009 15:01:23 -0600
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> >> +@tindex gdb.Frame
> >> +@tindex Frame
>
> Eli> Please don't use @tindex, we don't use such an index in the GDB
> Eli> manual.
>
> Now that we have documentation describing types, it seems like we
> ought to add a type index.
What's wrong with having them documented in the main index? We can
always have something like
@cindex @code{Foo}, a data type
More than one index in a manual complicates looking up things, and I
don't feel the number of types we have in GDB, or will have in the
near future, justifies this inconveniency. But I'm open to arguments
to the contrary.
next prev parent reply other threads:[~2009-03-17 22:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 18:00 Thiago Jung Bauermann
2009-03-10 23:37 ` Eli Zaretskii
2009-03-15 18:35 ` Thiago Jung Bauermann
2009-03-15 19:30 ` Eli Zaretskii
2009-03-16 3:36 ` Thiago Jung Bauermann
2009-03-16 4:07 ` Eli Zaretskii
2009-03-20 23:04 ` Thiago Jung Bauermann
2009-03-21 8:34 ` Eli Zaretskii
2009-03-30 5:33 ` Thiago Jung Bauermann
2009-03-30 18:35 ` Eli Zaretskii
2009-03-30 19:09 ` Tom Tromey
2009-03-30 19:24 ` Thiago Jung Bauermann
2009-03-30 19:57 ` Tom Tromey
2009-03-30 20:50 ` Thiago Jung Bauermann
2009-03-22 16:00 ` Tom Tromey
2009-03-17 21:13 ` Tom Tromey
2009-03-17 22:43 ` Eli Zaretskii [this message]
2009-03-18 0:35 ` Tom Tromey
2009-03-18 4:12 ` Eli Zaretskii
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=uhc1rrebj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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