From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] add "continue" response to pager
Date: Tue, 24 Jun 2014 18:11:00 -0000 [thread overview]
Message-ID: <87d2dy2n4o.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83tx7aqnr0.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 24 Jun 2014 19:24:35 +0300")
Eli> Thanks, but what about updating the manual?
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index b686271..3b298ea 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+2014-06-24 Tom Tromey <tromey@redhat.com>
+
+ * gdb.texinfo (Screen Size): Document "c" response to pagination
+ prompt.
+
2014-06-19 Gary Benson <gbenson@redhat.com>
* gdb.texinfo (Maintenance Commands): Document new
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 8588f73..0d519c6 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -22107,8 +22107,9 @@ Print ten commands just after the commands last printed.
Certain commands to @value{GDBN} may produce large amounts of
information output to the screen. To help you read all of it,
@value{GDBN} pauses and asks you for input at the end of each page of
-output. Type @key{RET} when you want to continue the output, or @kbd{q}
-to discard the remaining output. Also, the screen width setting
+output. Type @key{RET} when you want to continue the output, @kbd{q}
+to discard the remaining output, or @kbd{c} to disable paging for the
+rest of the current command. Also, the screen width setting
determines when to wrap lines of output. Depending on what is being
printed, @value{GDBN} tries to break the line at a readable place,
rather than simply letting it overflow onto the following line.
next prev parent reply other threads:[~2014-06-24 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 16:17 Tom Tromey
2014-06-24 16:24 ` Eli Zaretskii
2014-06-24 18:11 ` Tom Tromey [this message]
2014-06-24 18:48 ` Eli Zaretskii
2014-06-25 20:16 ` Doug Evans
2014-06-25 9:24 ` Gary Benson
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=87d2dy2n4o.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--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