From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org, gdb-patches@sourceware.org,
jan.vrany@labware.com
Subject: Re: [PATCH 2/2] gdb/python: implement support for sending custom MI async notifications
Date: Mon, 11 Sep 2023 16:43:21 +0300 [thread overview]
Message-ID: <83bke8rfk6.fsf@gnu.org> (raw)
In-Reply-To: <87cyyolw49.fsf@redhat.com> (message from Andrew Burgess on Mon, 11 Sep 2023 13:42:14 +0100)
> From: Andrew Burgess <aburgess@redhat.com>
> Cc: Jan Vrany <jan.vrany@labware.com>, Eli Zaretskii <eliz@gnu.org>
> Date: Mon, 11 Sep 2023 13:42:14 +0100
>
> > +@subsubsection @sc{gdb/mi} Notifications In Python
> > +
> > +@cindex MI notifications in python
> > +@cindex notifications in python, GDB/MI
> > +@cindex python notifications, GDB/MI
>
> I think these @cindex entries are supposed to appear at least before the
> @subsubsection heading, that way, when following the link from the index
> you'll be taken to the relevant heading rather than the body text -
> though I could be wrong about this, Eli might have some thoughts.
No, what you say is correct for @item, but not for sectioning
commands. In the latter case, we want to index entry to land the
reader on the text, not on the section name.
next prev parent reply other threads:[~2023-09-11 13:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 21:05 [PATCH 1/2] gdb/python: generalize serialize_mi_result() Jan Vrany
2023-09-08 21:05 ` [PATCH 2/2] gdb/python: implement support for sending custom MI async notifications Jan Vrany
2023-09-09 6:39 ` Eli Zaretskii
2023-09-11 12:42 ` Andrew Burgess
2023-09-11 13:02 ` Jan Vraný
2023-09-11 13:43 ` Eli Zaretskii [this message]
2023-09-11 14:22 ` Andrew Burgess
2023-09-11 14:14 ` Andrew Burgess
2023-09-12 10:58 ` Jan Vraný
2023-09-12 13:07 ` Andrew Burgess
2023-09-12 13:45 ` Jan Vraný
2023-09-12 13:53 ` Andrew Burgess
2023-09-11 14:21 ` Andrew Burgess
2023-09-11 14:24 ` Jan Vraný
2023-09-11 14:18 ` [PATCH 1/2] gdb/python: generalize serialize_mi_result() Andrew Burgess
2023-09-12 16:35 ` Tom Tromey
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=83bke8rfk6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.vrany@labware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).