From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [6.1] TUI in doco?
Date: Thu, 25 Mar 2004 16:26:00 -0000 [thread overview]
Message-ID: <4063081C.4010401@gnu.org> (raw)
In-Reply-To: <9681-Tue23Mar2004214811+0200-eliz@elta.co.il>
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
>>> Date: Mon, 22 Mar 2004 16:30:24 -0500
>>> From: Andrew Cagney <cagney@gnu.org>
>>>
>>> The attached is hopefully getting there.
>
>
> Thanks. My comments below.
>
>
>>> I also noticed an inconsistency in its name. "Terminal User
>>> Interface" is what HP use, it fixes that as well.
>
>
> FWIW, the previous interpretation of TUI was better: it's a text-mode
> UI; "terminal" doesn't necessarily imply "text-mode". Oh well...
>
>
>>> +@pindex @code{gdbtui}
>
>
> There's no need to use @code in @pindex entries, these entries are
> automatically typeset in the same typeface as arguments of @code.
I've removed this entry. That leaves just the entry pointing at the
chapter proper.
>>> +Activate the Terminal User Interface when starting. The Terminal User
>
>
> The first occurence of "Terminal User Interface" would look better in
> @dfn. Also, a @cindex entry for "Terminal User Interface" somewhere,
> probably where you have an index entry for TUI, could be a good idea.
Done (it's now text user interface).
>>> +The TUI is enabled by invoking @value{GDBN} using either
>>> +@pindex gdbtui
>>> +@samp{gdbtui} or @samp{gdb -tui}.
>
>
> This is the second time we have a @pindex entry about gdbtui; one of
> them is redundant and should be removed, I think.
Ok, see attached.
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 3121 bytes --]
2004-03-22 Andrew Cagney <cagney@redhat.com>
* gdb.texinfo (TUI): Delete reference to --enable-tui. Mention
"gdbtui".
(Mode Options): Mention "gdbtui".
(TUI): Rename chapter to "Terminal User Interface".
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.200
diff -u -r1.200 gdb.texinfo
--- doc/gdb.texinfo 9 Mar 2004 16:16:35 -0000 1.200
+++ doc/gdb.texinfo 22 Mar 2004 21:27:30 -0000
@@ -142,7 +142,7 @@
* Configurations:: Configuration-specific information
* Controlling GDB:: Controlling @value{GDBN}
* Sequences:: Canned sequences of commands
-* TUI:: @value{GDBN} Text User Interface
+* TUI:: @value{GDBN} Terminal User Interface
* Interpreters:: Command Interpreters
* Emacs:: Using @value{GDBN} under @sc{gnu} Emacs
* Annotations:: @value{GDBN}'s annotation interface.
@@ -1112,12 +1112,14 @@
@c resolve the situation of these eventually
@item -tui
@cindex @code{--tui}
-Activate the Terminal User Interface when starting.
-The Terminal User Interface manages several text windows on the terminal,
-showing source, assembly, registers and @value{GDBN} command outputs
-(@pxref{TUI, ,@value{GDBN} Text User Interface}).
-Do not use this option if you run @value{GDBN} from Emacs
-(@pxref{Emacs, ,Using @value{GDBN} under @sc{gnu} Emacs}).
+@pindex @code{gdbtui}
+Activate the Terminal User Interface when starting. The Terminal User
+Interface manages several text windows on the terminal, showing
+source, assembly, registers and @value{GDBN} command outputs
+(@pxref{TUI, ,@value{GDBN} Terminal User Interface}). Alternatively,
+the Terminal User Interface can be enabled by invoking the program
+@samp{gdbtui}. Do not use this option if you run @value{GDBN} from
+Emacs (@pxref{Emacs, ,Using @value{GDBN} under @sc{gnu} Emacs}).
@c @item -xdb
@c @cindex @code{--xdb}
@@ -13886,7 +13888,7 @@
@value{GDBN} which support @sc{gdb/mi} version 2 (or greater).
@node TUI
-@chapter @value{GDBN} Text User Interface
+@chapter @value{GDBN} Terminal User Interface
@cindex TUI
@menu
@@ -13897,12 +13899,14 @@
* TUI Configuration:: TUI configuration variables
@end menu
-The @value{GDBN} Text User Interface, TUI in short,
-is a terminal interface which uses the @code{curses} library
-to show the source file, the assembly output, the program registers
-and @value{GDBN} commands in separate text windows.
-The TUI is available only when @value{GDBN} is configured
-with the @code{--enable-tui} configure option (@pxref{Configure Options}).
+The @value{GDBN} Terminal User Interface, TUI in short, is a terminal
+interface which uses the @code{curses} library to show the source
+file, the assembly output, the program registers and @value{GDBN}
+commands in separate text windows.
+
+The TUI is enabled by invoking @value{GDBN} using either
+@pindex gdbtui
+@samp{gdbtui} or @samp{gdb -tui}.
@node TUI Overview
@section TUI overview
next prev parent reply other threads:[~2004-03-25 16:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 22:54 Andrew Cagney
2004-03-17 5:59 ` Eli Zaretskii
2004-03-19 0:09 ` Eli Zaretskii
2004-03-22 21:30 ` Andrew Cagney
2004-03-23 19:51 ` Eli Zaretskii
2004-03-25 16:26 ` Andrew Cagney [this message]
2004-03-25 20:30 ` Eli Zaretskii
2004-03-25 20:40 ` Andrew Cagney
2004-03-26 9:44 ` Eli Zaretskii
2004-03-26 16:23 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` [6.1] TUI in doco? (compiler errors) Manoj Iyer
2004-03-16 23:21 ` Manoj Iyer
2004-03-25 22:40 ` 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=4063081C.4010401@gnu.org \
--to=cagney@gnu.org \
--cc=eliz@elta.co.il \
--cc=gdb-patches@sources.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