From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31292 invoked by alias); 8 Apr 2008 20:38:13 -0000 Received: (qmail 31284 invoked by uid 22791); 8 Apr 2008 20:38:13 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 08 Apr 2008 20:37:56 +0000 Received: from zps75.corp.google.com (zps75.corp.google.com [172.25.146.75]) by smtp-out.google.com with ESMTP id m38Kbl58004802 for ; Tue, 8 Apr 2008 21:37:48 +0100 Received: from rn-out-0910.google.com (rnge24.prod.google.com [10.38.207.24]) by zps75.corp.google.com with ESMTP id m38Kbgm7007065 for ; Tue, 8 Apr 2008 13:37:47 -0700 Received: by rn-out-0910.google.com with SMTP id e24so2373502rng.1 for ; Tue, 08 Apr 2008 13:37:46 -0700 (PDT) Received: by 10.114.102.1 with SMTP id z1mr8157844wab.56.1207687066580; Tue, 08 Apr 2008 13:37:46 -0700 (PDT) Received: by 10.115.107.18 with HTTP; Tue, 8 Apr 2008 13:37:46 -0700 (PDT) Message-ID: Date: Wed, 09 Apr 2008 00:35:00 -0000 From: "Doug Evans" To: "Eli Zaretskii" Subject: Re: Strangeness in set command Cc: "Andrew STUBBS" , msnyder@specifix.com, drow@false.org, schwab@suse.de, gdb@sources.redhat.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080405185423.GB13805@caradoc.them.org> <1207595159.31772.330.camel@localhost.localdomain> <47FB4FAA.9000107@st.com> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-04/txt/msg00069.txt.bz2 On Tue, Apr 8, 2008 at 11:56 AM, Eli Zaretskii wrote: > > From: Andrew STUBBS > > Eli Zaretskii wrote: > > > Or maybe, if the text after "set " has a `=' character in it, we > > > should ask whether the user really meant "set variable". IOW, refuse > > > to obey this shortcut, even if it's unambiguous. > > > > > > > Hmmm, that's not great for set args: > > > > (gdb) set args --command=myscript > > That one could be special-cased. There's also prompt, env, and others. Maybe the thing to do is key off of var_string, etc., except that one can pass expressions for integer/boolean vars. Does the command parser know in time what it's working with?