From: nickrob@snap.net.nz (Nick Roberts)
To: Tom Tromey <tromey@redhat.com>
Cc: "Marc Khouzam" <marc.khouzam@ericsson.com>, <gdb@sourceware.org>,
gdb-patches@sourceware.org
Subject: [PATCH] util.c + doc [was Re: [RFC] Queries and frontends]
Date: Wed, 29 Jul 2009 23:56:00 -0000 [thread overview]
Message-ID: <19056.57733.247579.68268@totara.tehura.co.nz> (raw)
In-Reply-To: <m3r5vztcpw.fsf@fleche.redhat.com>
> I tend to think that the more generic change would be safe, and cleaner.
This should do it.
--
Nick http://www.inet.net.nz/~nickrob
2009-07-30 Nick Roberts <nickrob@snap.net.nz>
* utils.c (defaulted_query): Don't ask for confirmation if server
prefix is used.
2009-07-30 Nick Roberts <nickrob@snap.net.nz>
* gdb.texinfo (Server Prefix): Explain that server prefix suppresses
confirmation request.
*** utils.c.~1.215.~ 2009-07-22 15:29:54.000000000 +1200
--- utils.c 2009-07-30 11:39:08.000000000 +1200
*************** defaulted_query (const char *ctlstr, con
*** 1436,1443 ****
}
/* Automatically answer the default value if the user did not want
! prompts. */
! if (! caution)
return def_value;
/* If input isn't coming from the user directly, just say what
--- 1436,1443 ----
}
/* Automatically answer the default value if the user did not want
! prompts or the command was issued with the server prefix. */
! if (! caution || server_command)
return def_value;
/* If input isn't coming from the user directly, just say what
*** gdb.texinfo.~1.609.~ 2009-07-29 18:47:32.000000000 +1200
--- gdb.texinfo 2009-07-30 11:49:16.000000000 +1200
*************** The server prefix does not affect the re
*** 25607,25612 ****
--- 25607,25616 ----
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 irrespective of the value of
+ the @code{show confirm} command (@pxref{Messages/Warnings, ,Optional
+ Warnings and Messages}).
+
@node Prompting
@section Annotation for @value{GDBN} Input
next prev parent reply other threads:[~2009-07-29 23:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 3:18 [RFC] Queries and frontends Marc Khouzam
2009-07-21 6:13 ` Nick Roberts
2009-07-21 8:26 ` Hui Zhu
2009-07-21 8:29 ` Hui Zhu
2009-07-21 11:51 ` Nick Roberts
2009-07-22 6:11 ` Hui Zhu
2009-07-21 17:57 ` Michael Snyder
2009-07-21 18:37 ` Marc Khouzam
2009-07-21 18:55 ` Daniel Jacobowitz
2009-07-21 23:29 ` Nick Roberts
2009-07-22 13:38 ` Marc Khouzam
2009-07-26 5:04 ` Tom Tromey
2009-07-27 1:52 ` Nick Roberts
2009-07-27 16:17 ` Tom Tromey
2009-07-28 1:55 ` Nick Roberts
2009-07-29 21:13 ` Tom Tromey
2009-07-29 23:56 ` Nick Roberts [this message]
2009-07-30 0:28 ` [PATCH] util.c + doc [was Re: [RFC] Queries and frontends] Marc Khouzam
2009-07-30 3:13 ` Eli Zaretskii
2009-08-04 16:32 ` [PATCH] util.c + doc Tom Tromey
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=19056.57733.247579.68268@totara.tehura.co.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=tromey@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