This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [PATCH] Removal of markup annotations
> > That seems sensible. I can see now that "History" is in "Controlling GDB"
> > because it describes the setting of parameters. However, I think the
> > "Commands" section might be a better place.
>
> No, I think "Controlling GDB" is the right place, since
> history-related features are really about controlling the debugger.
> By contrast, "Commands" is a name that doesn't convey any real
> information about what's in it and what's not, since almost everything
> is a command in GDB.
"Controlling GDB" is a bit of a hotchpotch and seems to describe the setting
of parameters for which no other suitable place could be found. "Commands"
describes the general properties of commands without reference to any
particular one. That is why I think "Command history" and, indeed, "Command
editing" would fit there. But its your choice.
Nick
2005-06-22 Nick Roberts <nickrob@snap.net.nz>
* gdb.texinfo (History) Rename "Command History".
(Command History): Move node "Server Prefix" from section on
Annotations here.
*** gdb.texinfo 19 Jun 2005 15:00:52 +1200 1.270
--- gdb.texinfo 22 Jun 2005 11:42:10 +1200
***************
*** 1188,1194 ****
@item
Reads the command history recorded in the @dfn{history file}.
! @xref{History}, for more details about the command history and the
files where @value{GDBN} records it.
@end enumerate
--- 1188,1194 ----
@item
Reads the command history recorded in the @dfn{history file}.
! @xref{Command History}, for more details about the command history and the
files where @value{GDBN} records it.
@end enumerate
***************
*** 15023,15029 ****
@menu
* Prompt:: Prompt
* Editing:: Command editing
! * History:: Command history
* Screen Size:: Screen size
* Numbers:: Numbers
* ABI:: Configuring the current ABI
--- 15023,15029 ----
@menu
* Prompt:: Prompt
* Editing:: Command editing
! * Command History:: Command history
* Screen Size:: Screen size
* Numbers:: Numbers
* ABI:: Configuring the current ABI
***************
*** 15091,15097 ****
interface. Users unfamiliar with @sc{gnu} Emacs or @code{vi} are
encouraged to read that chapter.
! @node History
@section Command history
@cindex command history
--- 15091,15097 ----
interface. Users unfamiliar with @sc{gnu} Emacs or @code{vi} are
encouraged to read that chapter.
! @node Command History
@section Command history
@cindex command history
***************
*** 15104,15109 ****
--- 15104,15119 ----
package, to provide the history facility. @xref{Using History
Interactively}, for the detailed description of the History library.
+ To issue a command to @value{GDBN} without affecting certain aspects of
+ the state which is seen by users, prefix it with @samp{server }. This
+ means that this command will not affect the command history, nor will it
+ affect @value{GDBN}'s notion of which command to repeat if @key{RET} is
+ pressed on a line by itself.
+
+ The server prefix does not affect the recording of values into the value
+ history; to print a value without recording it into the value history,
+ use the @code{output} command instead of the @code{print} command.
+
Here is the description of @value{GDBN} commands related to command
history.
***************
*** 20604,20610 ****
@menu
* Annotations Overview:: What annotations are; the general syntax.
- * Server Prefix:: Issuing a command without affecting user state.
* Prompting:: Annotations marking @value{GDBN}'s need for input.
* Errors:: Annotations for error messages.
* Invalidation:: Some annotations describe things now invalid.
--- 20614,20619 ----
***************
*** 20683,20702 ****
denotes a @samp{control-z} character) are annotations; the rest is
output from @value{GDBN}.
- @node Server Prefix
- @section The Server Prefix
- @cindex server prefix for annotations
-
- To issue a command to @value{GDBN} without affecting certain aspects of
- the state which is seen by users, prefix it with @samp{server }. This
- means that this command will not affect the command history, nor will it
- affect @value{GDBN}'s notion of which command to repeat if @key{RET} is
- pressed on a line by itself.
-
- The server prefix does not affect the recording of values into the value
- history; to print a value without recording it into the value history,
- use the @code{output} command instead of the @code{print} command.
-
@node Prompting
@section Annotation for @value{GDBN} Input
--- 20692,20697 ----