From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6078 invoked by alias); 17 Apr 2012 22:59:23 -0000 Received: (qmail 6070 invoked by uid 22791); 17 Apr 2012 22:59:22 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_NO 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; Tue, 17 Apr 2012 22:59:09 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id CA6231C615A; Tue, 17 Apr 2012 18:59:08 -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 I8KxwuVruM4c; Tue, 17 Apr 2012 18:59:08 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 8F4F81C6146; Tue, 17 Apr 2012 18:59:08 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id C050D145616; Tue, 17 Apr 2012 15:59:00 -0700 (PDT) Date: Tue, 17 Apr 2012 23:01:00 -0000 From: Joel Brobecker To: Jan Kratochvil Cc: gdb-patches@sourceware.org Subject: Re: [cancel] [patch] More suggestive error_is_running message Message-ID: <20120417225900.GP2852@adacore.com> References: <20120410191907.GA31331@host2.jankratochvil.net> <20120411152531.GD2852@adacore.com> <20120411153457.GA22022@host2.jankratochvil.net> <20120411164522.GE2852@adacore.com> <20120417212234.GA21359@host2.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120417212234.GA21359@host2.jankratochvil.net> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2012-04/txt/msg00522.txt.bz2 > In general GDB should always suggest possible solutions to a problem. > Stating just the problem may not be enough for the user. Agreed on that. I have learnt to appreciate git's helpful hints when something happens. We just need to find the right wording to avoid being too verbose and undoing some of the benefits of the work done earlier to cut on verbosity. I realize it is a little disingenous of me to put everything on the same level, as some of the verbose output that was removed was simply useless or redundant, but I didn't know how to express it concisely. Anyway, what I was also trying to say is that my comments where meant to try to help with the wording. More often than not, I'll settle for something that works, or is good enough, even if it's not perfect. We both use English as a second language, so it's normal that we're having a tougher time writing good English error messages. -- Joel