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 responsible > 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 appear > would be great, if it's possible.
I think that what'd be very useful is: - some kind of separator - some timestamp (à la Org? with or without seconds) - some language info? - a referrer to the code block (like the =comments= in tangled files) The separator could even be (why not?) a Org heading: the entire output buffer could be an Org file, allowing for folding of less useful entries, or sparse tree searches: --8<---------------cut here---------------start------------->8--- * 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 */ --8<---------------cut here---------------end--------------->8--- Just a proposition example... For me, whatever the format... Best regards, Seb -- Sébastien Vauban _______________________________________________ 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
