From: Ton van Overbeek <v-overbeek@cistron.nl>
To: Stephane Carrez <stcarrez@nerim.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: TUI, secondary prompts do not work
Date: Mon, 28 Oct 2002 13:49:00 -0000 [thread overview]
Message-ID: <3.0.6.32.20021028224950.007ad100@127.0.0.1> (raw)
In-Reply-To: <3DBA8FAF.4070801@nerim.fr>
At 14:50 10/26/2002 +0200, Stephane Carrez wrote:
>Thanks for the report.
>
>It was a bug in the TUI and not in the way gdb manages prompts.
>See http://sources.redhat.com/ml/gdb-patches/2002-10/msg00561.html
Checked your fix, and I can confirm it fixes the problem.
It is (as expected) a much better fix than the one I proposed.
Merci beaucoup for including it on both main-line and 5.3 branch.
I still have some other TUI problems I am working on. These are:
- configure test should check for (n)curses when --enable-tui
(now it also accepts termcap). Cygwin check for (n)curses is wrong
and produces the wrong Makefile (links with -ltermcap instear of -lncurses).
- first TUI screen (after starting gdb and entering tui with C-X A)
is garbled. Needs a 'refresh' command to draw correctly.
- changing window heights with 'wh' works only partially because
command window is not treated correctly (Curses info for command window
is not updated).
- Handling of terminal window resize (SIGWINCH) not working on Cygwin.
All these are on a Cygwin system.
As soon as I have some more concrete info and fixes I'll report back.
Ton van Overbeek
next prev parent reply other threads:[~2002-10-28 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 7:03 Ton van Overbeek
2002-10-26 3:51 ` Stephane Carrez
2002-10-28 13:49 ` Ton van Overbeek [this message]
2002-10-29 8:03 ` Christopher Faylor
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=3.0.6.32.20021028224950.007ad100@127.0.0.1 \
--to=v-overbeek@cistron.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=stcarrez@nerim.fr \
/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