From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6249 invoked by alias); 30 Jul 2009 04:40:37 -0000 Received: (qmail 6236 invoked by uid 22791); 30 Jul 2009 04:40:37 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.25) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 30 Jul 2009 04:40:29 +0000 Received: from totara (223.63.255.123.dynamic.snap.net.nz [123.255.63.223]) by viper.snap.net.nz (Postfix) with ESMTP id 943B03DA505; Thu, 30 Jul 2009 16:40:27 +1200 (NZST) Received: by totara (Postfix, from userid 1000) id 7A4A8C160; Thu, 30 Jul 2009 16:40:26 +1200 (NZST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19057.9274.357301.662062@totara.tehura.co.nz> Date: Thu, 30 Jul 2009 07:24:00 -0000 To: "Marc Khouzam" Cc: "Tom Tromey" , Subject: RE: [PATCH] util.c + doc [was Re: [RFC] Queries and frontends] In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA07CA09F1@ecamlmw720.eamcs.ericsson.se> References: <6D19CA8D71C89C43A057926FE0D4ADAA07C00023@ecamlmw720.eamcs.ericsson.se> <19045.23703.743876.775308@totara.tehura.co.nz> <19053.2107.342469.683795@totara.tehura.co.nz> <19054.23189.193878.534661@totara.tehura.co.nz> <19056.57733.247579.68268@totara.tehura.co.nz> <6D19CA8D71C89C43A057926FE0D4ADAA07CA09F1@ecamlmw720.eamcs.ericsson.se> From: nickrob@snap.net.nz (Nick Roberts) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-07/txt/msg00733.txt.bz2 > Doesn't this amount to using "set confirm off"? > I might have missed it, but I don't remember why you didn't want > use that instead? In the console, the user can type "set confirm on/off" according to his preference. This change ensures that confirmation isn't required for commands that the frontend runs behind the users back independently of this setting, provided they are prefixed with "server". This is only for CLI commands and does not affect frontends which use GDB/MI. > And this solution does not help (some) frontends with > answering 'y' to nquery() nquery will indeed default to 'n'. > How about: > > if (! caution) > return def_value; > > if (server_command) > return 1; That might give surprising results, e.g. accidentally setting pending breakpoints. AFAIK this change is for _one_ frontend (Emacs) to use _one_ command (record stop). I think too much generality detracts from this objective as, unlike GDB/MI, the plan is not to develop annotations. -- Nick http://www.inet.net.nz/~nickrob