From: Andrew Cagney <cagney@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] "tui"
Date: Wed, 11 Feb 2004 14:47:00 -0000 [thread overview]
Message-ID: <402A4086.9020702@gnu.org> (raw)
In-Reply-To: <20040211131122.GA2333@white>
> On Tue, Feb 10, 2004 at 12:53:26PM -0700, Kevin Buettner wrote:
>
>> On Tue, 10 Feb 2004 13:40:10 -0500
>> Daniel Jacobowitz <drow@mvista.com> wrote:
>>
>
>> > On Tue, Feb 10, 2004 at 01:32:13PM -0500, Andrew Cagney wrote:
>
>> > >
>> > > This modifies the build machinery so that the program "tui" is built.
>> > > "tui" starts up GDB's TUI (or Text User Interface). Alternative program
>> > > names include "tgdb", "gdbtui", ...
>> > >
>> > > Comments? Otherwize look to commit it round 16th Feb.
>
>> >
>> > Any of those names sound great to me. I think that one with "gdb" in it
>> > would be clearer; unlike Insight, the TUI does not have a separate life
>> > from GDB.
>
>>
>> I too would prefer one of the names with "gdb" in it somewhere.
>
>
> I would also, I actually like the name gdbtui. It is clear that it is
> GDB, and it is clear that it is the text user interface.
Then:
tui<tab>
or
tg<tab>
wouldn't work.
Speaking of which, if that tcl/tk code ever integrated into GDB's code
base (assuming it's first contributed), it to will need a name: tclgdb,
tkgdb, and even gdbtk come to mind (ah, the ultimate irony).
Andrew
next prev parent reply other threads:[~2004-02-11 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 18:32 Andrew Cagney
2004-02-10 18:40 ` Daniel Jacobowitz
2004-02-10 19:53 ` Kevin Buettner
2004-02-11 13:11 ` Bob Rossi
2004-02-11 14:47 ` Andrew Cagney [this message]
2004-02-11 15:00 ` Bob Rossi
2004-02-12 4:34 ` Christopher Faylor
2004-02-10 19:11 ` Eli Zaretskii
2004-02-10 20:47 ` Andrew Cagney
2004-02-11 6:27 ` Eli Zaretskii
2004-02-18 18:53 ` Andrew Cagney
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=402A4086.9020702@gnu.org \
--to=cagney@gnu.org \
--cc=bob@brasko.net \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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