From: Dan Davison <dandavison7@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: [Babel] Error output buffer
Date: Tue, 23 Nov 2010 15:05:29 +0000 [thread overview]
Message-ID: <87pqtwrsg6.fsf@gmail.com> (raw)
In-Reply-To: <87ipzonmgg.fsf@gmail.com> (Eric Schulte's message of "Tue, 23 Nov 2010 07:28:31 -0700")
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.eric@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 <wxhgmqzgwmuf@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
next prev parent reply other threads:[~2010-11-23 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 10:03 [Babel] Error output buffer Sébastien Vauban
2010-11-23 14:06 ` Dan Davison
2010-11-23 14:28 ` Eric Schulte
2010-11-23 15:05 ` Dan Davison [this message]
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 \
--in-reply-to=87pqtwrsg6.fsf@gmail.com \
--to=dandavison7@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
--cc=wxhgmqzgwmuf@spammotel.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).