Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Tue, 05 Jun 2018 14:44:00 -0000	[thread overview]
Message-ID: <838t7tb8cz.fsf@gnu.org> (raw)
In-Reply-To: <87h8mi441j.fsf@tromey.com> (message from Tom Tromey on Mon, 04	Jun 2018 15:47:52 -0600)

> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org, eliz@gnu.org
> Date: Mon, 04 Jun 2018 15:47:52 -0600
> 
> Hi Eli, not sure if you saw Pedro's question in this thread:
> 
> Pedro> I'd suggest saying something here closer to gdb's output.  For example,
> Pedro> above, "continue the output" doesn't suggest that it's only one more
> Pedro> page, and, using the verb "continue" for the "c" key I think makes it
> Pedro> easier to memorize / understand.  Like so:
> 
> Pedro>  Type @key{RET} when you want to see one more page of output, @kbd{q}
> Pedro>  to discard the remaining output, or @kbd{c} to continue without paging
> Pedro>  for the rest of the current command.
> 
> Pedro> No need to post a new patch for that, if Eli's OK with it.

I'm OK with that.  Sorry for missing the cue.


      reply	other threads:[~2018-06-05 14:44 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
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 [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=838t7tb8cz.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