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

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

 > "value of `show confirm' command" sounds awkward (a command cannot
 > have a value).  Can you suggest a better wording?

Perhaps it's enough to say that they are disabled and point to the existing
description.

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


Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.613
diff -c -p -r1.613 gdb.texinfo
*** gdb.texinfo	3 Aug 2009 12:39:00 -0000	1.613
--- gdb.texinfo	4 Aug 2009 10:08:55 -0000
*************** Displays how many symbol complaints @val
*** 17972,17977 ****
--- 17972,17978 ----
  
  @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:
*************** The server prefix does not affect the re
*** 25664,25669 ****
--- 25665,25672 ----
  history; to print a value without recording it into the value history,
  use the @code{output} command instead of the @code{print} command.
  
+ It also disables confirmation requests (@pxref{confirmation requests}).
+ 
  @node Prompting
  @section Annotation for @value{GDBN} Input