From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Subject: Re: [Babel] Error output buffer Date: Sat, 27 Nov 2010 00:11:11 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Hi Eric, "Eric Schulte" wrote: > Sébastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes: >> 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: >> >> * 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 */ > > These are great ideas, in the case of single block execution I think we're > fine with the current behavior of a cleared error buffer containing only a > single error output, It certainly is already much better, though -- trying *on purpose* to play the devil's advocate -- we can imagine one would like to see the output of different executions at different times: I'm writing some code, testing, getting an error, updating the code, testing, and would like to see what diff it made with regard to the previous execution. > but in the case of multiple block evaluations (e.g. chained code blocks or > during export) I think that the above suggestions are great. I especially > like the idea of one Org-mode top-level heading per error. For your info, it's already what I'm doing with the messages from my .emacs file: at some points, I call:* (message "* Org mode stuff") and (message "** Org clocking stuff") so that I can easily switch my Messages buffer to org-mode and collapse sections which don't interest me at that point in time... > I've added this to the Babel task stack. Thanks a lot. Best regards, Seb -- Sébastien Vauban _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode-mXXj517/zsQ@public.gmane.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2010-11-26 23:11 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 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 [this message]
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 \ --email@example.com \ --firstname.lastname@example.org \ --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \ --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).