From: Jan Kratochvil <jkratoch@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [pushed] Fix PR tui/21216: TUI line breaks regression
Date: Fri, 10 Mar 2017 17:27:00 -0000 [thread overview]
Message-ID: <20170310172744.GA7009@host1.jankratochvil.net> (raw)
In-Reply-To: <4593d5aa-00c7-75a9-9fc6-b65bddad0c0a@redhat.com>
On Fri, 10 Mar 2017 18:20:18 +0100, Pedro Alves wrote:
> Or maybe do something different.
Yes, I do know all these problems. This is why I was going to separate TUI
output to a different project (with its own non-TCL testsuite) along with
separating MI, and replacing it all by some sane RPC variant later.
https://git.jankratochvil.net/?p=gdbmicli.git;a=summary
But you ditched that and you were right, there are other debuggers which
already do it the right way.
Jan
next prev parent reply other threads:[~2017-03-10 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 0:19 Pedro Alves
2017-03-09 23:04 ` Jan Kratochvil
2017-03-10 12:59 ` Jan Kratochvil
2017-03-10 13:33 ` Pedro Alves
2017-03-10 14:04 ` Jan Kratochvil
2017-03-10 17:20 ` Pedro Alves
2017-03-10 17:27 ` Jan Kratochvil [this message]
2017-03-10 18:17 ` Pedro Alves
2017-03-10 18:46 ` Jan Kratochvil
2017-03-10 18:55 ` 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=20170310172744.GA7009@host1.jankratochvil.net \
--to=jkratoch@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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