From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Davison Subject: Re: [Babel] Error output buffer Date: Tue, 23 Nov 2010 14:06:26 +0000 Message-ID: <87bp5g9lst.fsf@gmail.com> References: <80ipzoxsoo.fsf@missioncriticalit.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=41231 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PKtWz-0003zK-Do for emacs-orgmode@gnu.org; Tue, 23 Nov 2010 09:07:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PKtWr-0000R0-Bm for emacs-orgmode@gnu.org; Tue, 23 Nov 2010 09:07:37 -0500 Received: from plane.gmane.org ([80.91.229.3]:52124) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PKtWr-0000Qm-6V for emacs-orgmode@gnu.org; Tue, 23 Nov 2010 09:07:29 -0500 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1PKtWi-0006vM-Ke for emacs-orgmode@gnu.org; Tue, 23 Nov 2010 15:07:20 +0100 In-Reply-To: <80ipzoxsoo.fsf@missioncriticalit.com> (=?utf-8?Q?=22S=C3=A9b?= =?utf-8?Q?astien?= Vauban"'s message of "Tue, 23 Nov 2010 11:03:51 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: =?utf-8?Q?S=C3=A9bastien?= Vauban Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org S=C3=A9bastien Vauban writes: > Hi, > > A quick wished feature, if you agree on its usefulness. > > Currently, all error messages are concatenated to the same buffer, execut= ion > after execution, which makes it *difficult to distinguish between the new > errors*, and the ones already seen previously. Hi Seb, I agree, that had been bothering me too. I had fixed it a week or so ago in my local set up, and I've just pushed that to master. It wipes the error buffer clean at the start of execution (on C-c C-c, and during export). Dan > > Different propositions: > > - delete the contents of the buffer before every code execution > > - add something visible after every execution, like a separator line or a= ^L > character (new page, than can easily be displayed as a rule) > > - always show the last lines in a different color > > - in the same spirit, use two alternate colors for the messages (like in = some > HTML tables, for odd/even rows) > > - add a timestamp with the date, before every code execution. > > This is not exhaustive, just some (funny for some of them) ideas I have in > mind in order to make the messages more visible than they currently are. > > Thanks. > > Best regards, > Seb