Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] command trace / source verbose mode
Date: Wed, 16 Nov 2005 20:11:00 -0000	[thread overview]
Message-ID: <ubr0k74p7.fsf@gnu.org> (raw)
In-Reply-To: <437B6228.8010103@st.com> (message from Andrew STUBBS on Wed, 16 Nov 2005 16:45:28 +0000)

> Date: Wed, 16 Nov 2005 16:45:28 +0000
> From: Andrew STUBBS <andrew.stubbs@st.com>
> 
> +  add_setshow_boolean_cmd ("commandtrace", no_class, &commandtrace, _("\
> +Set tracing of GDB CLI commands."), _("\
> +Show state of GDB CLI command tracing."), _("\
> +When 'on', each command executed is displayed."),

The last sentence will read better if it is rephrased as follows:

  When 'on', each command is displayed as it is executed.

> Index: src/gdb/doc/gdb.texinfo

Thanks.  Please take care of the following gotchas, and then the
documentation patch can go in when the code is approved.

> +Execute @value{GDBN} commands from file @var{file}.

It is better to say

  Execute @value{GDBN} commands from the named @var{file}.

> +If you need to debug user-defined commands or sourced files you may find it
> +useful to enable command tracing. In this mode each command will be printed
                                   ^^
Need two blanks here.

> +If @code{-v}, for verbose mode, is given then then each command will
                                            ^^^^^^^^^
One "then" too much.

> +be displayed as it is executed. The option may be given before or after
                                 ^^
Need two blanks here.


  reply	other threads:[~2005-11-16 19:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 18:01 Andrew STUBBS
2005-11-16 20:11 ` Eli Zaretskii [this message]
2005-11-17 16:21   ` Andrew STUBBS
2006-07-06 13:16     ` Daniel Jacobowitz
2006-07-06 17:23       ` Andrew STUBBS
2006-07-06 17:33         ` Daniel Jacobowitz
2006-07-07 16:18           ` Andrew STUBBS
2006-07-08 12:02             ` Eli Zaretskii
2006-07-20 16:46               ` Andrew STUBBS
2006-07-20 19:24                 ` Eli Zaretskii
2006-07-21 14:48                   ` Andrew STUBBS
2006-07-21 14:49                     ` Daniel Jacobowitz
2006-07-20 19:38                 ` 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=ubr0k74p7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrew.stubbs@st.com \
    --cc=gdb-patches@sources.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