Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PING: [RFA/doco] document "set/show interactive-mode"
Date: Wed, 09 Sep 2009 19:17:00 -0000	[thread overview]
Message-ID: <8363bs2al9.fsf@gnu.org> (raw)
In-Reply-To: <20090909180355.GE20694@adacore.com>

> Date: Wed, 9 Sep 2009 11:03:55 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> 
> Looks like this one fell through the cracks.

Yes, sorry.  It was sitting in my inbox all this time.

> +@cindex Miscellaneous Settings

Index entries should not use capital letters in simple words.  Our
convention is to use only lower-case text.

> +  add_setshow_auto_boolean_cmd ("interactive-mode", class_support,
> +                                &interactive_mode, _("\
> +Set whether gdb should run in interactive mode or not"), _("\

"gdb" or "GDB"?

> +If on, gdb runs in interactive mode and waits for the user to answer\n\
> +all its queries.  If off, gdb runs in non-interactive mode and\n\
> +automatically assumes the default answer to all its queries.  If auto\n\
> +(which is the default), automatically determine which mode to use based\n\
> +on the standard input settings"),

A couple of minor stylistic comments:

 . For "on" and "off", you use "gdb runs", but for "auto" you say
   "automatically determine", which is inconsistent.  "gdb determines"
   in the latter case or "run" in the former case is more consistent.
   (I like the second alternative better, as it's more concise.)

 . I would lose the "automatically" part in the last sentence, since
   "auto" already says that.

Finally, what about NEWS?


  reply	other threads:[~2009-09-09 19:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 18:13 Joel Brobecker
2009-09-09 18:04 ` PING: " Joel Brobecker
2009-09-09 19:17   ` Eli Zaretskii [this message]
2009-09-10  0:58     ` Joel Brobecker
2009-09-10  3:14       ` Eli Zaretskii
2009-09-10 18:58         ` Joel Brobecker

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=8363bs2al9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.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