From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eric Schulte" Subject: Re: Re: [Babel] Error output buffer Date: Fri, 26 Nov 2010 13:37:55 -0700 Message-ID: <878w0flt24.fsf@gmail.com> References: <80ipzoxsoo.fsf@missioncriticalit.com> <87ipzn92nt.fsf@ucl.ac.uk> <80tyj7ohc1.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=45174 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PM53T-0002t9-TS for emacs-orgmode@gnu.org; Fri, 26 Nov 2010 15:38:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PM53S-00085H-I4 for emacs-orgmode@gnu.org; Fri, 26 Nov 2010 15:38:03 -0500 Received: from mail-pv0-f169.google.com ([74.125.83.169]:64660) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PM53S-00085A-As for emacs-orgmode@gnu.org; Fri, 26 Nov 2010 15:38:02 -0500 Received: by pvc30 with SMTP id 30so2091385pvc.0 for ; Fri, 26 Nov 2010 12:38:01 -0800 (PST) In-Reply-To: <80tyj7ohc1.fsf@missioncriticalit.com> (=?utf-8?Q?=22S=C3=A9b?= =?utf-8?Q?astien?= Vauban"'s message of "Tue, 23 Nov 2010 22:33:50 +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 S=C3=A9bastien Vauban writes: > Hi Eric, > > Eric S Fraga wrote: >>> - add something visible after every execution, like a separator line or= a >>> ^L character (new page, than can easily be displayed as a rule) >> >> I like this one (above), especially if you could append the date+time to= the >> formfeed and, ideally, some indication of the source code block responsi= ble >> for what follows. The latter is important because I often have multiple >> source code blocks with the same language and it would be nice to >> distinguish between them in terms of error output. Having the srcname ap= pear >> would be great, if it's possible. > > I think that what'd be very useful is: > > - some kind of separator > - some timestamp (=C3=A0 la Org? with or without seconds) > - some language info? > - a referrer to the code block (like the =3Dcomments=3D in tangled files) > > The separator could even be (why not?) a Org heading: the entire output b= uffer > could be an Org file, allowing for folding of less useful entries, or spa= rse > tree searches: > > * 2010-11-23 Tue 22:29:11 sh block > /* [[file:~/src/test.org::*Commands][Commands:1]] */ > Invalid command: ls\r > Invalid command: date\r > /* Commands:1 ends here */ > These are great ideas, in the case of single block execution I think we're fine with the current behavior of a cleared error buffer containing only a single error output, but in the case of multiple block evaluations (e.g. chained code blocks or during export) I think that the above suggestions are great. I especially like the idea of one Org-mode top-level heading per error. I've added this to the Babel task stack. Cheers -- Eric > > Just a proposition example... For me, whatever the format... > > Best regards, > Seb