From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA v2] Add "continue" response to pager
Date: Sun, 27 May 2018 21:01:00 -0000 [thread overview]
Message-ID: <83k1rp856r.fsf@gnu.org> (raw)
In-Reply-To: <87in79znmh.fsf@tromey.com> (message from Tom Tromey on Sat, 26 May 2018 23:14:14 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
> Date: Sat, 26 May 2018 23:14:14 -0600
>
> commit ccd0b974d93f5a87b33fdfb38eea7ed12b00fca0
> Author: Tom Tromey <tom@tromey.com>
> Date: Wed Apr 25 08:52:00 2018 -0600
>
> Add "continue" response to pager
>
> This adds a "continue" response to the pager. If the user types "c"
> in response to the pager prompt, pagination will be disabled for the
> duration of one command -- but re-enabled afterward. This is handy if
> you type a command that produces a lot of output, and you don't want
> to baby-sit it by typing "return" each time the prompt comes up.
>
> I think this version addresses all review comments from versions 1-3.
>
> Tested by the buildbot.
>
> ChangeLog
> 2018-05-26 Tom Tromey <tom@tromey.com>
>
> PR cli/12326:
> * NEWS: Add entry about pager.
> * utils.c (pagination_disabled_for_command): New global.
> (prompt_for_continue): Allow "c" response to prompt.
> (reinitialize_more_filter): Clear
> pagination_disabled_for_command.
> (fputs_maybe_filtered): Check pagination_disabled_for_command.
>
> doc/ChangeLog
> 2018-05-26 Tom Tromey <tom@tromey.com>
>
> PR cli/12326:
> * gdb.texinfo (Screen Size): Document "c" response to pagination
> prompt.
>
> testsuite/ChangeLog
> 2018-05-26 Tom Tromey <tom@tromey.com>
>
> PR cli/12326:
> * gdb.cp/static-print-quit.exp: Update.
> * lib/gdb.exp (pagination_prompt): Update.
> * gdb.base/page.exp: Use pagination_prompt. Add new tests.
> * gdb.python/python.exp: Use pagination_prompt.
Thanks, this is okay for the documentation parts.
next prev parent reply other threads:[~2018-05-27 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 14:52 Tom Tromey
2018-05-09 15:43 ` Tom Tromey
2018-05-09 19:51 ` Pedro Alves
2018-05-09 21:28 ` Tom Tromey
2018-05-10 0:23 ` Pedro Alves
2018-05-27 15:20 ` Tom Tromey
2018-05-27 21:01 ` Eli Zaretskii [this message]
2018-05-28 18:57 ` Pedro Alves
2018-05-29 9:03 ` Tom Tromey
2018-05-29 17:04 ` Pedro Alves
2018-06-04 21:47 ` Tom Tromey
2018-06-05 14:44 ` 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=83k1rp856r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tom@tromey.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).