Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: Stephane.Carrez@worldnet.fr
Cc: gdb@sources.redhat.com
Subject: Re: where should TUI documentation go?
Date: Fri, 20 Jul 2001 00:53:00 -0000	[thread overview]
Message-ID: <7263-Fri20Jul2001104004+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3B57589A.7A1AD35A@worldnet.fr>

> Date: Fri, 20 Jul 2001 00:00:58 +0200
> From: Stephane Carrez <Stephane.Carrez@worldnet.fr>
> 
> I plan to write a small documentation about the TUI.

Good plan! ;-)

> I've not seen anything about it in the gdb docs.

Right, there _is_ nothing there about the TUI.

> Where in the GDB documentation should this be inserted?
> 
>   gdb.texi  ?
>   gdbgui.texi  ?

I'd suggest to put the user-level stuff (commands, command-line
switches, etc.) in gdb.texinfo, while developer-level stuff (general
structure of TUI code, important high-level functions that application
code might wish to call, etc.) should go into gdbint.texinfo.

As for gdbgui.texinfo, its purpose is not clear to me (I once asked
here about that, but got zero responses).  It's obviously very old and
probably outdated.  It is also not part of the GDB manual, but rather
a separate manual; I don't think we should tell users to read two
manuals.

So I'm inclined to add all the up-to-date and relevant stuff about the
various UIs into gdb.texinfo (or make it @include gdbgui.texinfo,
provided that someone says gdbgui.texinfo is still accurate enough to
be useful).


  reply	other threads:[~2001-07-20  0:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-19 14:56 Stephane Carrez
2001-07-20  0:53 ` Eli Zaretskii [this message]
2001-07-20 15:43   ` Andrew Cagney
2001-07-26  0:30     ` Eli Zaretskii

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=7263-Fri20Jul2001104004+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=Stephane.Carrez@worldnet.fr \
    --cc=gdb@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