From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] Clean up wrap_here function a little
Date: Wed, 26 Jan 2022 15:21:00 -0700 [thread overview]
Message-ID: <874k5q9m0j.fsf@tromey.com> (raw)
In-Reply-To: <20211231222527.2930519-1-tom@tromey.com> (Tom Tromey's message of "Fri, 31 Dec 2021 15:25:23 -0700")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> One oddity in gdb is that wrap_here doesn't take a stream parameter.
Tom> This is a historical relic from before my involvement in gdb, but it
Tom> leads to kind of weird code that intermixes calls to wrap_here (which
Tom> only affects gdb_stdout) with writes to other streams.
Tom> This series is a step toward cleaning this up. It's part of a larger
Tom> project to un-spaghettify gdb's output pager.
I'm checking this in now.
Tom
prev parent reply other threads:[~2022-01-26 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 22:25 Tom Tromey
2021-12-31 22:25 ` [PATCH 1/4] Convert wrap_here to use integer parameter Tom Tromey
2021-12-31 22:25 ` [PATCH 2/4] Add ui_file::wrap_here Tom Tromey
2021-12-31 22:25 ` [PATCH 3/4] Always call the wrap_here method Tom Tromey
2021-12-31 22:25 ` [PATCH 4/4] Remove global wrap_here function Tom Tromey
2022-01-26 22:21 ` Tom Tromey [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=874k5q9m0j.fsf@tromey.com \
--to=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).