Hi Eric, Seb, 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, | | 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 `---- Hopfully this is a step in the right direction, although it doesn't resolve all the problems you outline. Dan "Eric Schulte" <schulte.e...@gmail.com> 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ébastien Vauban <wxhgmqzgw...@spammotel.com> writes: > >> Hi, >> >> A quick wished feature, if you agree on its usefulness. >> >> Currently, all error messages are concatenated to the same buffer, execution >> 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 _______________________________________________ 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