emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <dandavison7@gmail.com>
To: "Sébastien Vauban"
	<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: [Babel] Error output buffer
Date: Tue, 23 Nov 2010 14:06:26 +0000	[thread overview]
Message-ID: <87bp5g9lst.fsf@gmail.com> (raw)
In-Reply-To: <80ipzoxsoo.fsf@missioncriticalit.com> ("Sébastien Vauban"'s message of "Tue, 23 Nov 2010 11:03:51 +0100")



Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
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.

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

>
> 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

  reply	other threads:[~2010-11-23 14:07 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 [this message]
2010-11-23 14:28 ` Eric Schulte
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 \
    --in-reply-to=87bp5g9lst.fsf@gmail.com \
    --to=dandavison7@gmail.com \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org \
    /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).