From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17474 invoked by alias); 21 Jun 2005 23:47:35 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 17443 invoked by uid 22791); 21 Jun 2005 23:47:29 -0000 Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 21 Jun 2005 23:47:29 +0000 Received: from farnswood.snap.net.nz (p198-tnt1.snap.net.nz [202.124.110.198]) by viper.snap.net.nz (Postfix) with ESMTP id AF16B54C973; Wed, 22 Jun 2005 11:47:24 +1200 (NZST) Received: by farnswood.snap.net.nz (Postfix, from userid 501) id F1CF662A99; Wed, 22 Jun 2005 00:48:41 +0100 (BST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17080.42841.160763.150088@farnswood.snap.net.nz> Date: Tue, 21 Jun 2005 23:47:00 -0000 To: Eli Zaretskii Cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH] Removal of markup annotations In-Reply-To: References: <17071.40307.949193.158796@farnswood.snap.net.nz> <17078.44751.122166.148138@farnswood.snap.net.nz> <17079.14802.440872.208976@farnswood.snap.net.nz> <17079.49877.427388.19313@farnswood.snap.net.nz> X-SW-Source: 2005-06/txt/msg00340.txt.bz2 > > 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 * 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 ----