From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 95242 invoked by alias); 19 Jun 2019 13:40:23 -0000 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 Received: (qmail 95220 invoked by uid 89); 19 Jun 2019 13:40:23 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=HContent-Transfer-Encoding:8bit X-HELO: mailsec101.isp.belgacom.be Received: from mailsec101.isp.belgacom.be (HELO mailsec101.isp.belgacom.be) (195.238.20.97) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 19 Jun 2019 13:40:21 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=skynet.be; i=@skynet.be; q=dns/txt; s=securemail; t=1560951621; x=1592487621; h=message-id:subject:from:to:date:in-reply-to:references: mime-version:content-transfer-encoding; bh=pwfMBGsoQwplv8ZyuUuW2jMk+wyDsC9weTozh3VVUtw=; b=jRSV83svb7H54CxsEcS59iaZ2dwlRJq4iU+vRL9vCr6S02L3FrS6DFRL AkNT7jglhG268eSxRWiHqT4IbTS/YQ==; Received: from unknown (HELO md) ([109.128.218.96]) by relay.skynet.be with ESMTP/TLS/AES256-GCM-SHA384; 19 Jun 2019 15:40:19 +0200 Message-ID: <1560951618.8865.15.camel@skynet.be> Subject: Re: [PATCH v2 0/4] Introduce the "with" command From: Philippe Waroquiers To: Pedro Alves , gdb-patches@sourceware.org Date: Wed, 19 Jun 2019 13:40:00 -0000 In-Reply-To: <594eaa7a-3e28-74e7-c5a1-2f9297a8d5d9@redhat.com> References: <20190618003902.19805-1-palves@redhat.com> <1560904492.8865.12.camel@skynet.be> <594eaa7a-3e28-74e7-c5a1-2f9297a8d5d9@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2019-06/txt/msg00376.txt.bz2 On Wed, 2019-06-19 at 14:05 +0100, Pedro Alves wrote: > I'm thinking that the errors talking about "set" instead of > "with" can be seen as a feature.  If you consider the prefixed > case, like "with print foo", the error is telling you where > to look at the available settings for that prefix. Yes, I think this is a good approach, and the error messages are very clear. Thanks Philippe