From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Vladimir Prus <vladimir@codesourcery.com>,
gdb-patches@sources.redhat.com, nickrob@snap.net.nz
Subject: Re: MI solib notification
Date: Sun, 01 Feb 2009 17:53:00 -0000 [thread overview]
Message-ID: <20090201175309.GA4597@caradoc.them.org> (raw)
In-Reply-To: <utz7gzcmo.fsf@gnu.org>
On Fri, Jan 30, 2009 at 11:51:11PM +0200, Eli Zaretskii wrote:
> > From: Vladimir Prus <vladimir@codesourcery.com>
> > Date: Sat, 31 Jan 2009 00:10:46 +0300
> >
> > Are doc changes OK?
>
> Yes, thanks. But I have a few comments:
>
> > +@item =library-loaded,id="@var{id}",target-name="@var{target-name}",host-name="@var{host-name}",low-address="@var{low}",high-address="@var{high}",symbols-loaded="@var{loaded}"
>
> This is a very long line, and the @table that it's part of has @code
> markup, which means TeX will not break this line. We need to make it
> shorter. One idea is this:
>
> @item =library-loaded,@var{info}
>
> and then describe the contents of @var{info} below, perhaps as a
> separate @table. WDYT?
MI output comes all on one line, but what we've done elsewhere in the
GDB/MI chapter is insert line breaks after some of the commas. How
about that here too? This form is easy to visually parse, once you're
used to the MI syntax.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-02-01 17:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 23:44 Vladimir Prus
[not found] ` <utz7gzcmo.fsf@gnu.org>
2009-02-01 17:53 ` Daniel Jacobowitz [this message]
2009-02-01 18:22 ` Eli Zaretskii
2009-02-01 18:29 ` Daniel Jacobowitz
2009-02-17 19:09 ` Vladimir Prus
2009-02-17 19:45 ` Eli Zaretskii
2009-02-17 19:49 ` Vladimir Prus
2009-02-17 20:30 ` Eli Zaretskii
2009-02-17 21:45 ` Vladimir Prus
2009-02-17 21:59 ` Vladimir Prus
2009-02-18 7:31 ` Eli Zaretskii
2009-02-18 10:19 ` Vladimir Prus
2009-02-18 19:53 ` Eli Zaretskii
2009-02-18 20:04 ` Vladimir Prus
2009-02-18 22:28 ` Eli Zaretskii
2009-02-18 4:24 ` Eli Zaretskii
2009-02-17 21:37 ` Daniel Jacobowitz
2009-02-17 22:10 ` Pedro Alves
2009-02-18 2:01 ` Pedro Alves
2009-02-01 18:04 ` Daniel Jacobowitz
2009-02-12 9:12 ` Vladimir Prus
2009-02-12 13:22 ` Daniel Jacobowitz
2009-02-12 15:02 ` Vladimir Prus
2009-02-12 15:13 ` Daniel Jacobowitz
2009-02-12 17:35 ` Tom Tromey
2009-02-12 18:02 ` Daniel Jacobowitz
2009-02-12 20:11 ` Tom Tromey
2009-02-12 20:17 ` Vladimir Prus
2009-02-12 20:26 ` Daniel Jacobowitz
2009-02-17 19:08 ` Vladimir Prus
2009-02-12 18:06 ` Pedro Alves
2009-02-12 19:45 ` Pedro Alves
2009-02-12 19:56 ` Tom Tromey
2009-02-12 19:58 ` Daniel Jacobowitz
2009-02-13 2:22 ` Joel Brobecker
2009-02-01 18:47 ` Daniel Jacobowitz
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=20090201175309.GA4597@caradoc.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
--cc=vladimir@codesourcery.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