From: Andrew Cagney <cagney@gnu.org>
To: Stephane Carrez <stcarrez@nerim.fr>
Cc: gdb@sources.redhat.com
Subject: Re: GNUtify TUI code, enable TUI
Date: Thu, 08 Jan 2004 22:36:00 -0000 [thread overview]
Message-ID: <3FFDDB5A.50805@gnu.org> (raw)
In-Reply-To: <3FFDBCF9.5070904@nerim.fr>
>> Hi!
>>
>> Andrew Cagney wrote:
>> Hello,
>>
>> I think its time to GNUtify the TUI code. Actually, the code should have been GNUtifyed before that faitful first commit, however now is better late than never :-) (Stephane's been careful to ensure that any new code is GNUtiful, this will fix the old code). As for building theTUI by default, its been on the things-to-do-today list for too long :-( So the plan is:
>>
>> ~2004-01-10: Rename the files/functions. Mindless, tedious, but relatively "obvious".
>>
>> ~2004-01-17: Enable the TUI by default.
>>
>> comments,
>> Andrew
>
>
> Great! So you plan to have this for 6.1?
Yep, that's the intent. I'm hoping that this time I've started the
process early enough to make the branch date ...
> This reminds me some work I did last summer on TUI register window to
> cleanup the code and use the gdb new register API (and fix some bunch
> of problems...). Not committed because... lack of time? Valentin's birth?
>
> There is also this TUI testsuite I wrote. It works but for some
> reasons sometimes expect fails to recognize the output (:-
>
> I'll try to resurect my TUI reg fixes...
ya!
Andrew
prev parent reply other threads:[~2004-01-08 22:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 20:19 Andrew Cagney
2004-01-05 20:21 ` Daniel Jacobowitz
2004-01-06 6:09 ` Eli Zaretskii
2004-01-06 21:54 ` Andrew Cagney
2004-01-07 6:04 ` Eli Zaretskii
2004-01-07 14:58 ` Andrew Cagney
2004-01-07 17:39 ` Eli Zaretskii
2004-01-08 20:26 ` Stephane Carrez
2004-01-08 20:30 ` Daniel Jacobowitz
2004-01-08 22:36 ` Andrew Cagney [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=3FFDDB5A.50805@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@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