emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tom Gillespie <tgbugs@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>, akater <nuclearspace@gmail.com>
Subject: Re: [PATCH] Add support for trace and error output streams in Common Lisp
Date: Sat, 5 Sep 2020 13:07:52 -0700	[thread overview]
Message-ID: <CA+G3_PNOWak+rACQYkUMTW3oB69rGdhf9M73QFbn2N-z-NeXsw@mail.gmail.com> (raw)
In-Reply-To: <87eenhk0ym.fsf@gnu.org>


One comment on this patch right now is that =errors= should probably
be changed to =error= for consistency with the slime nomenclature and
with the fact that all the rest of the options for the :results header
are singular nouns.

I also wanted to chime in here with a note that this seems to fall
into a larger set of questions about standardization and
regularization of the org babel api that have appeared on the list
over the past couple of months.

I think that error has a clear and useful meaning for many languages
and it would be great to be able to capture it without resorting to
hackery like 2>&1 which
can't actually separate out the errors from the outputs when working in a shell.

I think this also points to a larger potential feature which is the ability to
capture and insert the output of multiple different streams at the same time
(more on that in a forthcoming mail on org-babel, which I might hold off on
until after the 9.4 release).


On Fri, Sep 4, 2020 at 8:37 AM Bastien <bzg@gnu.org> wrote:
> Let's continue to discuss this for after 9.4.

  reply	other threads:[~2020-09-05 20:08 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
2020-09-05 20:07       ` Tom Gillespie [this message]
2020-09-06  5:03         ` Bastien
2020-07-07 12:03   ` akater

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:

  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=CA+G3_PNOWak+rACQYkUMTW3oB69rGdhf9M73QFbn2N-z-NeXsw@mail.gmail.com \
    --to=tgbugs@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=nuclearspace@gmail.com \


* 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).