Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: RFA: fix CLI/9591 (pagination and --batch)
Date: Mon, 08 Mar 2010 18:13:00 -0000	[thread overview]
Message-ID: <83r5nu3cpn.fsf@gnu.org> (raw)
In-Reply-To: <m3zl2ivh9o.fsf@fleche.redhat.com>

> From: Tom Tromey <tromey@redhat.com>
> Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
> Date: Mon, 08 Mar 2010 10:45:55 -0700
> 
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> Eli> This is okay, but please also add notes to the two referenced nodes
> Eli> telling how the batch mode changes their respective defaults.
> 
> It doesn't change their defaults, it permanently overrides them.

Well, I don't see how that subtle difference matters here.  For
example, in the "Messages/Warnings" node the manual currently says:

    `set confirm off'
	 Disables confirmation requests.

    `set confirm on'
	 Enables confirmation requests (the default).

    `show confirm'
	 Displays state of confirmation requests.

What I had in mind is adding a note like this:

    @item set confirm off
    Disables confirmation requests.  Note that running @value{GDBN}
    with the @option{--batch} option (@pxref{Mode Options, --batch})
    also automatically disables confirmation requests.

and similarly for pagination.

> Here is a new version with a NEWS entry.  Please review.

They are okay otherwise.  Thanks.


  reply	other threads:[~2010-03-08 18:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 19:58 Tom Tromey
2010-03-05 20:51 ` Pedro Alves
2010-03-05 22:24   ` Tom Tromey
2010-03-05 23:45     ` Pedro Alves
2010-03-06  4:10     ` Joel Brobecker
2010-03-06  9:32       ` Eli Zaretskii
2010-03-06  9:14     ` Eli Zaretskii
2010-03-08 17:46       ` Tom Tromey
2010-03-08 18:13         ` Eli Zaretskii [this message]
2010-03-08 18:47           ` Tom Tromey
2010-03-08 19:11             ` Eli Zaretskii

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=83r5nu3cpn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=tromey@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