From: Dmitry Sivachenko <dima@Chg.RU>
To: eliz@is.elta.co.il
Cc: davidw@gordian.com, gdb-patches@sourceware.cygnus.com
Subject: Re: Include GDB/MI docs in GDB manual
Date: Wed, 19 Apr 2000 04:57:00 -0000 [thread overview]
Message-ID: <200004191151.PAA16650@netserv1.chg.ru> (raw)
In-Reply-To: <200004180901.FAA13035@indy.delorie.com>
> I think it is bad idea to make a 'garbage heap' from the GDB manual,
> mainly intended for regular GDB users, not 'GDB hackers'.
OK, I have nothing against including gdbmi.texi into GDB manual.
--dima
I tend to the opposite ;-)
I think that, ideally, the documentation should include everything in
a single place. If properly indexed, such a document, however large,
is a handy tool for finding any issue your are after, in a fast and
efficient way.
In contrast, cross-references between different manuals are usually
rare, and the facilities for searching multiple documents are abysmally
more primitive (and mostly unknown and unused) than what you have for
searching a single Info document.
Here's a simple demonstration: the GDB manual does not have a single
reference to the GDB Internals manual. How do we expect a user who
reads gdb.info to know that more docs about GDB is available
elsewhere?
Btw, the fact that "make install" in the GDB distro doesn't install
the Info docs, unlike any other GNU project I've seen, actually makes
it more probable that gdbint.info will not be installed anywhere along
INFOPATH. So even advanced features like "info --apropos" (how many
people around here even know about the --apropos switch?) might not
help.
prev parent reply other threads:[~2000-04-19 4:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.04.10004170753370.19907-100000@pcx08>
2000-04-17 8:56 ` Dmitry Sivachenko
[not found] ` <200004180901.FAA13035@indy.delorie.com>
2000-04-19 4:57 ` Dmitry Sivachenko [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=200004191151.PAA16650@netserv1.chg.ru \
--to=dima@chg.ru \
--cc=davidw@gordian.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sourceware.cygnus.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