From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17498 invoked by alias); 18 Sep 2009 14:37:37 -0000 Received: (qmail 17489 invoked by uid 22791); 18 Sep 2009 14:37:37 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 18 Sep 2009 14:37:33 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 9A9822BAB60; Fri, 18 Sep 2009 10:37:31 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id G0wHh5bhM1nM; Fri, 18 Sep 2009 10:37:31 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 9F9ED2BAB57; Fri, 18 Sep 2009 10:37:30 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id E8BA2F592B; Fri, 18 Sep 2009 07:37:17 -0700 (PDT) Date: Fri, 18 Sep 2009 14:37:00 -0000 From: Joel Brobecker To: Pedro Alves Cc: gdb-patches@sourceware.org, Hui Zhu , Tom Tromey , Marc Khouzam , Eli Zaretskii , Michael Snyder Subject: Re: Another proposal for frontends and queries. Message-ID: <20090918143717.GO8910@adacore.com> References: <200909181031.53507.pedro@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909181031.53507.pedro@codesourcery.com> User-Agent: Mutt/1.5.18 (2008-05-17) 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-09/txt/msg00592.txt.bz2 > Having just "" behave differently depending on a setting, is > bad UI/usability, IMO. If you switch to 'query', you force the user to > type 'y' or 'n' explicitly, which is a Good Thing. I agree. Hui: You keep suggesting more of the same - basically, your suggestions so far revolve around the same principle, which is adding an extra setting that controls the query being made. But we have already explained that this is something we would like to avoid, and we explained why. In the meantime, the issue remains unresolved and people like Marc continue being stuck with it. There are two aspects to this issue: 1. A specific short-term need: The default for queries in precord is 'n', and that causes auto-answers in Eclipse to be 'n' as well. As a result, Eclipse uses cannot use precord fully. The answer to that problem is very simple: Do *NOT* provide a default answer. That's what "query" does. 2. A longer-term issue: It should be possible for Front-Ends using GDB/MI to relay queries to the user, so that the user can enter confirmation before the operation is in fact executed. That's longer term, as this needs some infrastructure work. Right now, I'm only interested in (1). It's clear that you do not like the idea of querying the user without providing a default. Can you explain why? -- Joel