From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, dmalcolm@redhat.com
Subject: Re: [patch] Fix python gdb.execute to not paginate
Date: Fri, 06 Aug 2010 08:35:00 -0000 [thread overview]
Message-ID: <83k4o4w34e.fsf@gnu.org> (raw)
In-Reply-To: <20100805212008.GA12652@host1.dyn.jankratochvil.net>
> Date: Thu, 5 Aug 2010 23:20:08 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: David Malcolm <dmalcolm@redhat.com>
>
> gdb/doc/
> 2010-08-05 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdb.texinfo (Mode Options) <-batch>
> (Basic Python) <gdb.execute>: Describe setting width and height.
Thanks.
> 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. Batch mode also disables pagination;
> -@pxref{Screen Size} and acts as if @kbd{set confirm off} were in
> -effect (@pxref{Messages/Warnings}).
> +in the command files. Batch mode also disables pagination, sets unlimited
> +terminal width and height; @pxref{Screen Size} and acts as if @kbd{set confirm
^ ^
The semi-colon should be removed, and a comma added after @pxref's
closing brace.
> +return value is @code{None}. With @code{True} @var{to_string} the
> +@value{GDBN} virtual terminal has temporarily set unlimited width and height
> +with disabled pagination; @pxref{Screen Size}.
Suggest to rephrase as follows (assuming I got your intent correctly):
If @var{to_string} is @code{True}, the
@value{GDBN} virtual terminal will be temporarily set to unlimited width
and height, and its pagination will be disabled; @pxref{Screen Size}.
Okay with those changes.
prev parent reply other threads:[~2010-08-06 8:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 21:20 Jan Kratochvil
2010-08-06 0:49 ` Doug Evans
2010-08-06 1:22 ` Doug Evans
2010-08-06 17:15 ` Tom Tromey
2010-08-06 17:27 ` Doug Evans
2010-08-06 10:29 ` Jan Kratochvil
2010-08-06 21:37 ` Doug Evans
2010-08-07 15:02 ` Jan Kratochvil
2010-08-09 17:30 ` Tom Tromey
2010-08-09 19:24 ` Jan Kratochvil
2010-08-06 8:35 ` Eli Zaretskii [this message]
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=83k4o4w34e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmalcolm@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).