From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14405 invoked by alias); 24 Mar 2008 23:37:38 -0000 Received: (qmail 14396 invoked by uid 22791); 24 Mar 2008 23:37:38 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 24 Mar 2008 23:37:11 +0000 Received: from kahikatea.snap.net.nz (228.31.255.123.static.snap.net.nz [123.255.31.228]) by viper.snap.net.nz (Postfix) with ESMTP id 576BC3DA285; Tue, 25 Mar 2008 12:37:09 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 720288FC6D; Tue, 25 Mar 2008 11:37:01 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18408.15132.721049.31408@kahikatea.snap.net.nz> Date: Mon, 24 Mar 2008 23:37:00 -0000 To: Daniel Jacobowitz Cc: Pedro Alves , gdb-patches@sourceware.org Subject: Re: cleanup mi error message handling In-Reply-To: <20080324223840.GA20307@caradoc.them.org> References: <200803241830.11759.pedro@codesourcery.com> <18408.9553.683746.929167@kahikatea.snap.net.nz> <20080324223840.GA20307@caradoc.them.org> X-Mailer: VM 7.19 under Emacs 22.1.92.2 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/msg00372.txt.bz2 > > because the first goes to the console for the user to see, the second to > > the frontend to be handled as appropriate. > > Could you explain why the duplication here is good? It seems to me > that if the front end wants to display this error to the user in the > console, it can do so anyway, but it shouldn't have to. Maybe this > requires a version bump, I don't know. 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! > In Eclipse, this duplication leads to a bunch of error messages that > pop up in the console pane which don't come from anything the user > did. It's very confusing. 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? -- Nick http://www.inet.net.nz/~nickrob