Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Bob Wilson <bwilson@tensilica.com>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] fix some documentation menus
Date: Fri, 23 Mar 2007 23:11:00 -0000	[thread overview]
Message-ID: <46045EB3.8070503@tensilica.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 609 bytes --]

This patch fixes some out-of-order menu entries and removes some menus that 
don't match the hierarchical structure of the document.

It also removes some unnecessary next/prev/up arguments from a @node entry, 
since they can cause problems for conditional text and since none of the other 
nodes (except Top) specify those arguments.

OK?

2007-03-23  Bob Wilson  <bob.wilson@acm.org>

	* gdb.texinfo (Top): Move TUI and Annotations menu entries to match
	the order of the nodes.
	(C Operators, C Constants, Debugging C): Remove extra menus.
	(Method Names in Commands): Do not specify next/prev/up nodes.
	

[-- Attachment #2: gdb-doc-menus.patch --]
[-- Type: text/plain, Size: 2065 bytes --]

Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.389
diff -u -r1.389 gdb.texinfo
--- gdb.texinfo	26 Feb 2007 20:10:17 -0000	1.389
+++ gdb.texinfo	23 Mar 2007 23:02:09 -0000
@@ -144,11 +144,11 @@
 * Configurations::              Configuration-specific information
 * Controlling GDB::             Controlling @value{GDBN}
 * Sequences::                   Canned sequences of commands
-* TUI::                         @value{GDBN} Text User Interface
 * Interpreters::		Command Interpreters
+* TUI::                         @value{GDBN} Text User Interface
 * Emacs::                       Using @value{GDBN} under @sc{gnu} Emacs
-* Annotations::                 @value{GDBN}'s annotation interface.
 * GDB/MI::                      @value{GDBN}'s Machine Interface.
+* Annotations::                 @value{GDBN}'s annotation interface.
 
 * GDB Bugs::                    Reporting bugs in @value{GDBN}
 
@@ -9184,10 +9184,6 @@
 attempts to invoke the redefined version instead of using the operator's
 predefined meaning.
 
-@menu
-* C Constants::
-@end menu
-
 @node C Constants
 @subsubsection C and C@t{++} constants
 
@@ -9248,14 +9244,6 @@
 and @samp{@{&"hi", &"there", &"fred"@}} is a three-element array of pointers.
 @end itemize
 
-@menu
-* C plus plus expressions::
-* C Defaults::
-* C Checks::
-
-* Debugging C::
-@end menu
-
 @node C plus plus expressions
 @subsubsection C@t{++} expressions
 
@@ -9419,10 +9407,6 @@
 with pointers and a memory allocation function.  @xref{Expressions,
 ,Expressions}.
 
-@menu
-* Debugging C plus plus::
-@end menu
-
 @node Debugging C plus plus
 @subsubsection @value{GDBN} features for C@t{++}
 
@@ -9524,7 +9508,7 @@
 * The Print Command with Objective-C::
 @end menu
 
-@node Method Names in Commands, The Print Command with Objective-C, Objective-C, Objective-C
+@node Method Names in Commands
 @subsubsection Method Names in Commands
 
 The following commands have been extended to accept Objective-C method

             reply	other threads:[~2007-03-23 23:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-23 23:11 Bob Wilson [this message]
2007-03-24 17:18 ` 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=46045EB3.8070503@tensilica.com \
    --to=bwilson@tensilica.com \
    --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