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: Sat, 06 Mar 2010 09:14:00 -0000 [thread overview]
Message-ID: <831vfx4xt8.fsf@gnu.org> (raw)
In-Reply-To: <m3k4tqs8z7.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Fri, 05 Mar 2010 15:24:12 -0700
>
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -1028,7 +1028,9 @@ Run in batch mode. Exit with status @code{0} after processing all the
> command files specified with @samp{-x} (and all commands from
> initialization files, if not inhibited with @samp{-n}). Exit with
> nonzero status if an error occurs in executing the @value{GDBN} commands
> -in the command files.
> +in the command files. Batch mode also disables pagination;
> +@pxref{Screen Size} and acts as if @code{set confirm off} were in
> +effect (@pxref{Messages/Warnings}).
This is okay, but please also add notes to the two referenced nodes
telling how the batch mode changes their respective defaults.
Oh, and please use @kbd{set confirm off}, as that would be a command
typed at the keyboard.
> +/* True if --batch or --batch-silent was seen. */
> +int batch = 0;
Is it wise to have a global symbol with such a short and ``general''
name? Previously, it was static, so that was probably okay. Now it's
a true global, so it could potentially clash with some library. I'd
suggest to rename it to something less invasive.
Thanks.
next prev parent reply other threads:[~2010-03-06 9:14 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 [this message]
2010-03-08 17:46 ` Tom Tromey
2010-03-08 18:13 ` Eli Zaretskii
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=831vfx4xt8.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