From: "Eric Schulte" <firstname.lastname@example.org> To: "Sébastien Vauban" <email@example.com> Cc: firstname.lastname@example.org Subject: Re: [Babel] Error output buffer Date: Tue, 23 Nov 2010 07:28:31 -0700 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (=?utf-8?Q?=22S=C3=A9b?= =?utf-8?Q?astien?= Vauban"'s message of "Tue, 23 Nov 2010 11:03:51 +0100") 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 <email@example.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
next prev parent reply other threads:[~2010-11-23 14:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-23 10:03 Sébastien Vauban 2010-11-23 14:06 ` Dan Davison 2010-11-23 14:28 ` Eric Schulte [this message] 2010-11-23 15:05 ` Dan Davison 2010-11-23 20:59 ` Eric S Fraga 2010-11-23 21:33 ` Sébastien Vauban 2010-11-26 20:37 ` Eric Schulte 2010-11-26 23:11 ` Sébastien Vauban
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [Babel] Error output buffer' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).