Re: [PATCH] util.c + doc [was Re: [RFC] Queries and frontends]

[nickrob@snap.net.nz (Nick Roberts)]

 > Yes, that's good, but the sentence is too far from the first paragraph
 > of this section to make "It" self-explanatory.  How about the variant
 > below?
 > 
 >  The @code{server } prefix also disables confirmation requests
 >  (@pxref{confirmation requests}).


The phrase "The server prefix" is already used three lines earlier
(without @code).  How about:


*** gdb.texinfo	06 Aug 2009 15:42:03 +1200	1.614
--- gdb.texinfo	06 Aug 2009 17:07:08 +1200	
*************** Displays how many symbol complaints @val
*** 18009,18014 ****
--- 18009,18015 ----
  
  @end table
  
+ @anchor{confirmation requests}
  By default, @value{GDBN} is cautious, and asks what sometimes seems to be a
  lot of stupid questions to confirm certain commands.  For example, if
  you try to run a program which is already running:
*************** command to repeat if @key{RET} is presse
*** 25697,25705 ****
  means that commands can be run behind a user's back by a front-end in
  a transparent manner.
  
! 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
--- 25698,25710 ----
  means that commands can be run behind a user's back by a front-end in
  a transparent manner.
  
! The @code{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.
! 
! Using this prefix also disables confirmation requests
! (@pxref{confirmation requests}).
  
  @node Prompting
  @section Annotation for @value{GDBN} Input


-- 
Nick                                           http://www.inet.net.nz/~nickrob