From: Eli Zaretskii <eliz@gnu.org>
To: "Doug Evans" <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] new command to search memory
Date: Fri, 15 Feb 2008 08:28:00 -0000 [thread overview]
Message-ID: <u63wqk4j5.fsf@gnu.org> (raw)
In-Reply-To: <e394668d0802141451q37be78aepd9556e3911beb9d3@mail.gmail.com> (dje@google.com)
> Date: Thu, 14 Feb 2008 14:51:40 -0800
> From: "Doug Evans" <dje@google.com>
> Cc: gdb-patches@sourceware.org
>
> On Thu, Feb 14, 2008 at 11:53 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > > Date: Wed, 13 Feb 2008 18:19:15 -0800 (PST)
> > > From: dje@google.com (Doug Evans)
> >
> > >
> > > I didn't get a response to the non-doc portions of this patch.
> > > [Eli, thanks for the doc review, I made the suggested changes,
> > > though I went a different route in shortening the length of the
> > > line specifying the find command syntax. The end result is still
> > > rather short.]
> >
> > You mean, rather long...
> >
> > The patch is okay with me, but could you (or someone else) please see
> > whether these two long lines
> >
> >
> > > +@item find @r{[}/@var{sn}@r{]} @var{start_addr}, @@@var{len}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]}
> > > +@itemx find @r{[}/@var{sn}@r{]} @var{start_addr}, @var{end_addr}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]}
> >
> > survive the typesetting for the printed manual (either by TeX or
> > pdftex) without overflowing the page margin? I'm afraid they will
> > overflow, since the items of this table are typeset with @code, and
> > @code specifies a chunk of monospaced font that cannot be broken
> > between lines.
>
> Is looking at gdb.pdf (created with cd doc && make gdb.pdf) sufficient?
Yes, thanks.
next prev parent reply other threads:[~2008-02-15 8:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 2:20 Doug Evans
2008-02-14 19:54 ` Eli Zaretskii
2008-02-14 22:52 ` Doug Evans
2008-02-15 8:28 ` Eli Zaretskii [this message]
2008-02-16 5:39 ` Doug Evans
2008-02-16 13:33 ` Eli Zaretskii
2008-02-26 2:31 ` Daniel Jacobowitz
2008-02-29 3:13 ` Doug Evans
2008-02-29 3:58 ` Daniel Jacobowitz
2008-04-17 2:59 ` Doug Evans
2008-04-28 18:37 ` Fwd: " Doug Evans
2008-04-29 0:40 ` Eli Zaretskii
2008-05-09 6:46 ` Doug Evans
2008-05-09 14:35 ` Eli Zaretskii
2008-05-02 15:19 ` Daniel Jacobowitz
2008-05-09 6:35 ` Doug Evans
2008-05-09 7:33 ` Daniel Jacobowitz
2008-05-09 20:16 ` Doug Evans
2008-05-09 20:18 ` Daniel Jacobowitz
2008-04-09 21:06 ` Doug Evans
2008-05-02 15:37 ` 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=u63wqk4j5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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