From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Always disable pagination with MI?
Date: Wed, 03 Mar 2010 21:53:00 -0000 [thread overview]
Message-ID: <m3d3zl3wei.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201003032138.54319.pedro@codesourcery.com> (Pedro Alves's message of "Wed, 3 Mar 2010 21:38:54 +0000")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> Any objections to this?
Pedro> 2010-03-03 Pedro Alves <pedro@codesourcery.com>
Pedro> gdb/
Pedro> * utils.c (fputs_maybe_filtered): Always disable pagination if the
Pedro> top level interpreter is MI.
FWIW, it seems reasonable to me.
There is a related PR about disabling pagination when using --batch.
I wonder whether anybody would object to that?
Tom
next prev parent reply other threads:[~2010-03-03 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 21:39 Pedro Alves
2010-03-03 21:40 ` Pedro Alves
2010-03-03 21:53 ` Tom Tromey [this message]
2010-03-04 5:19 ` Joel Brobecker
2010-03-03 22:09 ` Vladimir Prus
2010-03-04 17:15 ` Marc Khouzam
2010-03-04 17:33 ` Pedro Alves
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=m3d3zl3wei.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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