From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Davison Subject: Re: [Babel] Error output buffer Date: Tue, 23 Nov 2010 15:05:29 +0000 Message-ID: <87pqtwrsg6.fsf@gmail.com> References: <80ipzoxsoo.fsf@missioncriticalit.com> <87ipzonmgg.fsf@gmail.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=46324 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PKuSs-0006vP-Ju for emacs-orgmode@gnu.org; Tue, 23 Nov 2010 10:08:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PKuRo-0006G4-JP for emacs-orgmode@gnu.org; Tue, 23 Nov 2010 10:07:25 -0500 Received: from markov.stats.ox.ac.uk ([163.1.210.1]:41383) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PKuRo-0006FI-9x for emacs-orgmode@gnu.org; Tue, 23 Nov 2010 10:06:20 -0500 In-Reply-To: <87ipzonmgg.fsf@gmail.com> (Eric Schulte's message of "Tue, 23 Nov 2010 07:28:31 -0700") 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: Eric Schulte Cc: =?utf-8?Q?S=C3=A9bastien?= Vauban , emacs-orgmode@gnu.org Hi Eric, Seb,=20 I'd actually just pushed my local fix that I had made to this so far. Our emails crossed because mine is being held up by gmane as I forgot to switch the obfuscated gmane reply address for the normal list address, but here's what will come through eventually: ,---- | Hi Seb, |=20 | 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). |=20 | Dan `---- Hopfully this is a step in the right direction, although it doesn't resolve all the problems you outline. Dan "Eric Schulte" writes: > 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, execu= tion >> 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 > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode