From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb@sources.redhat.com
Subject: Re: [docs] Naming on GDB/MI sections in docs
Date: Fri, 08 Jan 2010 19:54:00 -0000 [thread overview]
Message-ID: <83hbqw9xus.fsf@gnu.org> (raw)
In-Reply-To: <201001081840.44197.vladimir@codesourcery.com>
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Fri, 8 Jan 2010 18:40:44 +0300
>
>
> At present, the toc of documentation PDF looks like this:
>
> gdb
> 27 The gdb/mi Interface
> Function and Purpose
> Notation and Terminology
> 27.3 gdb/mi General Design
> 27.3.1 Context management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
> 27.3.2 Asynchronous command execution and non-stop mode . .
> 27.3.3 Thread groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
> 27.4 gdb/mi Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
> 27.4.1 gdb/mi Input Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ouch!
> 1. Why some section titles are started by "gdb/mi"? We're already
> inside "The gdb/mi Interface" section, so it's reasonable to assume
> subsections talk about gdb/mi.
When you look at the entire TOC, yes. But what if you land in that
section in Info, by following some cross-reference or index search?
> Can we remove those prefixes?
If others don't mind (and if the consideration I mention above doesn't
make you change your mind), then I won't object. Just make sure we
don't already have other sections by the same name.
> 2. Why is "Function and Purpose" subsection lacks section number in
> the TOC? I would have expected "27.1".
Because it's an @unnumberedsec for some reason. Change it to
@section, and you will have the number. The same goes for "Notation
and Terminology".
Thanks for spotting these blunders.
prev parent reply other threads:[~2010-01-08 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 15:40 Vladimir Prus
2010-01-08 19:54 ` Eli Zaretskii [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=83hbqw9xus.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=vladimir@codesourcery.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