Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA v2] Add "continue" response to pager
Date: Thu, 10 May 2018 00:23:00 -0000	[thread overview]
Message-ID: <6b0962b4-1867-0003-6310-e874ff1df2f3@redhat.com> (raw)
In-Reply-To: <87d0y44iyi.fsf@tromey.com>

On 05/09/2018 10:28 PM, Tom Tromey wrote:
>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
> 
> Pedro> I gave the patch a quick try, and I have to say that it looks a
> Pedro> bit odd to me that the pager prompt takes two lines:
> 
> Pedro> ---Type <return> to continue, q <return> to quit, or c <return> to
> Pedro>    continue without paging---
> 
> Pedro> I'm wondering whether we can shorten that, to, say:
> 
> Pedro> ---Type <return> for more, q to quit, c to continue without paging---
> 
> Yeah, I think that would be better.
> 
> The Emacs docs write <RET> for return.  So maybe:
> 
> Pedro> --Type <ret> for more, q to quit, c to continue without paging--       # 64 cols
> 
> Though I guess I would tend to add a couple of spaces, so:
> 
> -- Type <RET> for more, q to quit, c to continue without paging --       # 66 cols

That's fine with me.  I suspect that the "---" wrapping without
spaces might have been inspired by some Unix /usr/bin/more
implementation, because util-linux's 'more' prints "--More-- "
by default.

> I would like to get the spelling worked out before updating the patch.
> 
> Pedro> Did you look up the patch submission, see if it still makes sense?
> 
> Nope, but if we shorten the text then perhaps the change won't be
> needed.

A racy test won't usually be an issue with size of the text, but
about how the regexps might match differently depending
on how much the expect buffer happens to get filled with.

I found the original submission, here:

  https://sourceware.org/ml/gdb-patches/2011-05/msg00150.html

which points at:

 ~~~~~~~~~~~~
 However, when using read1(), the "<return>" part matches with
 this snippet from lib/gdb.exp:
 
          "<return>" {
             send_gdb "\n"
             perror "Window too small."
             fail "$message"
             ...
 ~~~~~~~~~~~~

However, someone *cough* changed that "<return>" to
$pagination_prompt instead:

	-re "$pagination_prompt" {
	    send_gdb "\n"
	    perror "Window too small."
	    fail "$message"

in:

commit c3f814a14336b9d395f3abad739592929e2faaa0
Author:     Pedro Alves <palves@redhat.com>
AuthorDate: Fri Jul 25 10:07:38 2014 +0100

    Fix paginate-*.exp races

so it looks like the split is really no longer necessary.

A brief passage about this in the commit log would be nice,
so that we have a history link in case we need to revisit.

Please confirm that the affected tests pass cleanly with
make check-read1, just to make sure.

Thanks,
Pedro Alves


  reply	other threads:[~2018-05-09 23:50 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 [this message]
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

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=6b0962b4-1867-0003-6310-e874ff1df2f3@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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