Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: keiths@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/MI] Event Records vs Commands
Date: Sat, 15 Jun 2002 10:33:00 -0000	[thread overview]
Message-ID: <4634-Sat15Jun2002203052+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <Pine.GSO.4.33.0206132206350.19373-100000@makita.cygnus.com> (message from Keith Seitz on Thu, 13 Jun 2002 22:24:36 -0700 (PDT))

> Date: Thu, 13 Jun 2002 22:24:36 -0700 (PDT)
> From: Keith Seitz <keiths@redhat.com>
> 
> This is the promised gdbmi.texinfo proposal that I referred to in:
> 
> http://sources.redhat.com/ml/gdb/2002-06/msg00106.html
> 
> This patch formalizes events in MI. Specifically, I propose to whack
> notify-async-output from aync-record and add event-record to
> out-of-band-record.

Thanks.  This is approved, but please take care of teh following
small problems:

> ! in @value{GDBN}. Events can be generated by any command, whether that command

Please always leave two spaces after a period that ends a sentence.
This is important for the printed version to be typeset correctly by
TeX.

> ! @item breakpoint-create
> ! @item breakpoint-modify
> ! @item breakpoint-delete
> ! @item tracepoint-create
> ! @item tracepoint-modify
> ! @item tracepoint-delete
> ! A breakpoint or tracepoint was created, modified, or deleted. In all cases,

You cannot lump several @item's together, the result will look badly.
All the @item's but the first need to be an @itemx instead.

> ! @example
> ! =breakpoint-create,number="1"
> ! @end example

I believe the general policy in the GDB manual is to use @smallexample
throughout.


  reply	other threads:[~2002-06-15 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13 22:24 Keith Seitz
2002-06-15 10:33 ` Eli Zaretskii [this message]
2002-06-15 11:46   ` Andreas Schwab
2002-06-15 19:01 ` Andrew Cagney
2002-06-15 19:10   ` Andrew Cagney
2002-06-18 11:34     ` Keith Seitz
2002-06-18 13:43       ` Eli Zaretskii
2002-06-25 20:17       ` Andrew Cagney
2002-06-17 10:25   ` Keith Seitz
2002-06-17 11:28     ` Andrew Cagney

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=4634-Sat15Jun2002203052+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=keiths@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