From: Bastien <firstname.lastname@example.org>
To: akater <email@example.com>
Subject: Re: [PATCH] Add support for trace and error output streams in Common Lisp
Date: Fri, 04 Sep 2020 17:37:05 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (akater's message of "Mon, 06 Jul 2020 21:58:32 +0000")
akater <firstname.lastname@example.org> writes:
> Sorry for the delay. The patch is now safe to apply.
No problem. We are in feature freeze for 9.4 so this cannot be
applied right now.
Also, it modifies ob-core.el by allow "errors" and "trace" outputs.
Before adding these optional output (just for Lisps?), let's think
whether they can be useful for other Babel languages.
> The feature is set to not activate until SLIME 2.28 which is likely
> months into the future.
It does not feel right to make changes in Org's core about something
that will (certainly) happen in an (uncertain) future. What is the
benefit for today? Maybe I miss something.
Finally, the complete patch should also update org-manual.org on top
Let's continue to discuss this for after 9.4.
next prev parent reply other threads:[~2020-09-04 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 3:32 [PATCH] Add support for trace and error output streams in Common Lisp akater
2020-04-18 13:05 ` akater
2020-06-02 12:03 ` Bastien
2020-07-06 21:58 ` akater
2020-09-04 15:37 ` Bastien [this message]
2020-09-05 20:07 ` Tom Gillespie
2020-09-06 5:03 ` Bastien
2020-07-07 12:03 ` 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).