From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20241 invoked by alias); 25 Mar 2008 01:00:08 -0000 Received: (qmail 20231 invoked by uid 22791); 25 Mar 2008 01:00:08 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 25 Mar 2008 00:59:44 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 89B18983C6; Tue, 25 Mar 2008 00:59:42 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 6C92B9810C; Tue, 25 Mar 2008 00:59:42 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JdxVt-0007Hd-5M; Mon, 24 Mar 2008 20:59:41 -0400 Date: Tue, 25 Mar 2008 01:00:00 -0000 From: Daniel Jacobowitz To: Nick Roberts Cc: Pedro Alves , gdb-patches@sourceware.org Subject: Re: cleanup mi error message handling Message-ID: <20080325005941.GA27677@caradoc.them.org> Mail-Followup-To: Nick Roberts , Pedro Alves , gdb-patches@sourceware.org References: <200803241830.11759.pedro@codesourcery.com> <18408.9553.683746.929167@kahikatea.snap.net.nz> <20080324223840.GA20307@caradoc.them.org> <18408.15132.721049.31408@kahikatea.snap.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18408.15132.721049.31408@kahikatea.snap.net.nz> User-Agent: Mutt/1.5.17 (2007-12-11) 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: 2008-03/txt/msg00373.txt.bz2 On Tue, Mar 25, 2008 at 11:37:00AM +1200, Nick Roberts wrote: > Emacs isn't currently using this output, so I'm not speaking from experience, > but how does the front end determine which messages are for the user? > > Currently most messages that are due to frontend errors go through error () > so I guess I'm suggesting the opposite change! Any time you call error, it should already be caught and show up in the ^error output. The GDB/MI documentation says that ~"" is for: `"~" STRING-OUTPUT' The console output stream contains text that should be displayed in the CLI console window. It contains the textual responses to CLI commands. > Just as you say if the "frontend wants to display this error to the user in > the console, it can do so anyway" isn't it equally true that if it doesn't want > to display this error, it can choose not to so? Yes, but unlike a formatted MI response, the front end doesn't know what a random bit of ~"output" is. It might be a notification, like a new thread, or an error message, or... -- Daniel Jacobowitz CodeSourcery