From: Eli Zaretskii <eliz@is.elta.co.il>
To: Stan Shebs <shebs@apple.com>
Cc: Andrew Cagney <ac131313@cygnus.com>,
gdb@sourceware.cygnus.com, ischis2@home.com
Subject: Re: Merging manuals (was Re: How do you use GDB to debug GDB)
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010321115859.24397S-100000@is> (raw)
In-Reply-To: <3AB7B697.CBAF2099@apple.com>
On Tue, 20 Mar 2001, Stan Shebs wrote:
> The arguments for merging are that it slightly simplifies document
> maintenance, and more importantly that it facilitates the transition
> from being a user of the tool to being a developer of it.
There's another important consideration: the ease of finding
information when you use the manual as a reference (as opposed to a
textbook which is read in its entirety).
The most efficient means of using a manual as a reference is the `i'
command of the Info browser. (For those who don't know: that command
looks up a string you type in the manual's indices, and in a
well-indexed manual, will usually land you on the right spot in a
matter of seconds.)
If that fails, the next best alternative is `s' which searches the
manual's text for a string or a regexp.
By contrast, the facilities presented by today's Info browsers for
searching multiple documents are abysmally inadequate. In the
stand-alone Info reader, we have the --apropos option (which I'm quite
sure some of the people here have never heard about); and we have
nothing similar in Emacs.
Also, please note that the chapters which describe annotations and
GDB/MI are already very technical in nature and come very close to
documenting the internals.
So I think, on balance, merging the two documents would be a good
thing.
next prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 15:59 How do you use GDB to debug GDB Michael Elizabeth Chastain
2001-03-21 15:59 ` Stephen Smith
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` Merging manuals (was Re: How do you use GDB to debug GDB) Stan Shebs
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Michael Meissner
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` Eli Zaretskii [this message]
2001-03-21 15:59 ` How do you use GDB to debug GDB Eli Zaretskii
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59 ` Stephen Smith
-- strict thread matches above, loose matches on Subject: below --
2001-03-21 15:59 Merging manuals (was Re: How do you use GDB to debug GDB) Michael Elizabeth Chastain
2001-03-21 15:59 ` Andrew Cagney
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59 ` Fernando Nasser
2001-03-21 15:59 ` Eli Zaretskii
2001-03-21 15:59 ` J.T. Conklin
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=Pine.SUN.3.91.1010321115859.24397S-100000@is \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=ischis2@home.com \
--cc=shebs@apple.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