From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jkratoch@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [pushed] Fix PR tui/21216: TUI line breaks regression
Date: Fri, 10 Mar 2017 18:55:00 -0000 [thread overview]
Message-ID: <89a44793-33db-6f95-a0b0-a51b0e1c2d11@redhat.com> (raw)
In-Reply-To: <20170310184637.GA20146@host1.jankratochvil.net>
On 03/10/2017 06:46 PM, Jan Kratochvil wrote:
>>> and you were right, there are other debuggers which
>>> already do it the right way.
>>
>> I don't think I ever said such a thing.
>
> You said something different although IMO with the same practical result.
That's an incorrect interpretation.
> This text from an internal list but I do not find that too secret:
>
> On Fri, 26 Jun 2015 18:44:11 +0200, Pedro Alves wrote:
> # Basically you're saying we should rewrite the whole CLI from scratch.
> # And it basically seems like writing a _different_ debugger from
> # scratch to me.
That I did say, but that "different" meant that it'd be a different
debugger in the user's perspective and in the use cases that it
could support. E.g., how with separate components in separate processes
you can't have an single integrated Python API.
Thanks,
Pedro Alves
prev parent reply other threads:[~2017-03-10 18:55 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
2017-03-10 18:17 ` Pedro Alves
2017-03-10 18:46 ` Jan Kratochvil
2017-03-10 18:55 ` Pedro Alves [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=89a44793-33db-6f95-a0b0-a51b0e1c2d11@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jkratoch@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