Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fwd: [RFA] new command to search memory
Date: Tue, 29 Apr 2008 00:40:00 -0000	[thread overview]
Message-ID: <u4p9lzuar.fsf@gnu.org> (raw)
In-Reply-To: <e394668d0804280706h70e36428yd8ba07abb44e086e@mail.gmail.com>

> Date: Mon, 28 Apr 2008 07:06:51 -0700
> From: "Doug Evans" <dje@google.com>
> 
> --- NEWS	4 Apr 2008 15:51:15 -0000	1.264
> +++ NEWS	17 Apr 2008 02:35:23 -0000

This part is okay, thanks.

> +	  printf_filtered (_("empty search range\n"));

Do we want to capitalize the messages (here and elsewhere in your
patch)?

> --- doc/gdb.texinfo	16 Apr 2008 13:14:18 -0000	1.481
> +++ doc/gdb.texinfo	17 Apr 2008 02:35:24 -0000

This part is also okay, but I have a few comments/corrections.

> +@table @code
> +@item b
> +Bytes.
> +@item h
> +Halfwords (two bytes).
> +@item w
> +Words (four bytes).
> +@item g
> +Giant words (eight bytes).
> +@end table

In this table, the text under @item's are not complete sentences, so
it's better to start them with a lowercase letter and not end them
with a period.

> +This means, for example, that if the current source language is C/C++

Please use C@t{++} for "C++", it looks better in print.

> +then searching for the string "hello" includes the trailing '\0'.

Please quote text ``like this'', rather than "like this", it looks
better in print (and will be translated into "like this" in the
on-line manual).

> +Note that this means, for example, that in the case of C-like languages
> +a search for an untyped 0x42 will search for "(int) 0x42"

Please use @samp{(int) 0x42}, to force use of typeface appropriate for
program symbols.

> +@item @var{n}, maximum number of finds
> +The maximum number of finds to print.  The default is to print all finds.

I think "matches" is a better word than "finds".

> +Strings may be specified for search values, quote them with double-quotes

It's better to avoid passive tense.  For example:

  You can use strings as search values.  Quote them with double-quotes
  (@code{"}).

> +For example, if stopped at the printf in this function:

"printf" should be in @code.

> +@smallexample
> +void
> +hello ()
> +@{
> +  static char hello[] = "hello-hello";
> +  static struct @{ char c; short s; int i; @} __attribute__ ((packed)) mixed

This last line is too long for a @smallexample.  Please break it into
two shorter lines.

> +You get during debugging:

This is a continuation of the sentence broken by @smallexample.  So
you should begin it with a lower-case `y', and you should put
@noindent (on a line of itself) immediately before it, to prevent
indentation that is typically output at the beginning of a paragraph.

Other than that, your changes for the documentation are okay with me.
Thanks!


  reply	other threads:[~2008-04-28 18:52 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
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 [this message]
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=u4p9lzuar.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