From: Bastien <firstname.lastname@example.org>
To: akater <email@example.com>
Subject: Re: (almost a patch) Receiving more output from a Common Lisp evaluation in Org buffer
Date: Sun, 24 May 2020 15:35:23 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (akater's message of "Wed, 08 Apr 2020 23:20:59 +0000")
akater <firstname.lastname@example.org> writes:
> I have a patch that allows to put trace output and error output into
> corresponding Org buffer.
Can you share the patch (as an attachment)?
Does it add a functionality just for one ob-* library or for babel
evaluation in general?
> Current behaviour with outputs being splitted
> so that they go to different buffers (Org buffer, REPL), is arbitrary
> and inconvenient. The patch ensures backwards compatibility. I thus
> believe merging the patch would be a clear improvement. I use the
> proposed features daily (trace, mostly). Note however that the patch
> can't be merged right away; see [[Caveats]].
Can the patch be made so that the ob-* library is still compatible
with previous versions of slime?
If the patch is just for one babel library and completely depends on
a version of slime that does not exist yet, perhaps it is a good idea
to publish your modified version of that library, test the proposed
feature with your users and see what can be added to Org's core later
Don't hesitate to send an update on this.
next prev parent reply other threads:[~2020-05-24 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 23:20 (almost a patch) Receiving more output from a Common Lisp evaluation in Org buffer akater
2020-05-24 13:35 ` Bastien [this message]
2020-05-25 0:21 ` stardiviner
2020-07-06 22:17 ` akater
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).