From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eric Schulte" Subject: Re: [Babel] Error output buffer Date: Tue, 23 Nov 2010 07:28:31 -0700 Message-ID: <87ipzonmgg.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=57618 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PKtrw-0006q6-AO for emacs-orgmode@gnu.org; Tue, 23 Nov 2010 09:29:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PKtrK-0005GU-Gd for emacs-orgmode@gnu.org; Tue, 23 Nov 2010 09:29:05 -0500 Received: from mail-vw0-f41.google.com ([209.85.212.41]:64883) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PKtrK-0005GE-9r for emacs-orgmode@gnu.org; Tue, 23 Nov 2010 09:28:38 -0500 Received: by vws10 with SMTP id 10so4256539vws.0 for ; Tue, 23 Nov 2010 06:28:37 -0800 (PST) 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: emacs-orgmode@gnu.org This is something that Dan and I have discussed as well. On the one hand it would be nice to wipe the buffer between block executions, but on the other hand when you are say exporting a file and running many code blocks at once it would be preferable to retain error messages from all of the code blocks. I've been thinking that either a we could delete the buffer form all manual entry points into code block execution so that it is refreshed between manual code block execs but not between automated (e.g. on export) code block execs. Another option would be to separate the error messages with timestamps as you've proposed, and maybe with some mark that can be jumped to with a keystroke. I'm not sure which approach would be best. -- Eric 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. > > 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