Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 18:46:00 -0000	[thread overview]
Message-ID: <20170310184637.GA20146@host1.jankratochvil.net> (raw)
In-Reply-To: <4f9a4e59-ccc8-9d6e-7ce2-f030f6efe184@redhat.com>

On Fri, 10 Mar 2017 19:17:20 +0100, Pedro Alves wrote:
> How you love pulling things out of context.  

Because everything is interconnected.


> Whatever testing you think would be appropriate for testing TUI/ncurses
> _output_ in your project, we can consider for GDB too.  If you have ideas
> for that, please share them.

I do not think a front end UI really needs any testsuite as it is a trivial
code (in a proper language and with proper API - not MI; MI is not API and not
proper).  That is not the case of a front end intertwingled into GDB core.

Besides that maybe one could fix a TUI frontend for the testsuite purposes.
I have no idea how much usable ncurses is with "dumb":
$ TERM=dumb gdb -tui
Cannot enable the TUI: terminal doesn't support cursor addressing [TERM=dumb]


> > 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.
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.


Jan


  reply	other threads:[~2017-03-10 18:46 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 [this message]
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=20170310184637.GA20146@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