From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] gdb: Don't flush line wrap buffer before adding newline
Date: Tue, 05 Feb 2019 15:27:00 -0000 [thread overview]
Message-ID: <87womentlq.fsf@tromey.com> (raw)
In-Reply-To: <20190205151016.2127-1-andrew.burgess@embecosm.com> (Andrew Burgess's message of "Tue, 5 Feb 2019 15:10:16 +0000")
>>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:
Andrew> * utils.c (fputs_maybe_filtered): Don't flush the line wrap buffer
Andrew> before inserting a newline for line-wrapping.
Thanks, this is ok. I actually have the same patch and a very similar
test on my branch to fix up the pager when styles are enabled. That
branch has a few more fixes, too; but it doesn't hurt to land this one
now.
Tom
next prev parent reply other threads:[~2019-02-05 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 15:10 Andrew Burgess
2019-02-05 15:27 ` Tom Tromey [this message]
2019-02-05 15:55 ` Andrew Burgess
2019-02-05 20:44 ` Tom Tromey
2019-02-05 17:15 ` Andrew Burgess
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=87womentlq.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.com \
--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