emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Tom Gillespie <tgbugs@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Ivar Fredholm <freddyholms@protonmail.com>,
	 "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
	ian martins <ianxm@jhu.edu>
Subject: Re: We have asynchronous sessions, why have anything else?
Date: Mon, 27 Jun 2022 15:04:24 -0700	[thread overview]
Message-ID: <CA+G3_PMD+OdN1=yfR79aFaJFXrNzsAbX328JtOWer5jKO+98zw@mail.gmail.com> (raw)
In-Reply-To: <87y1xio2cn.fsf@localhost>

> I am not even sure if all the babel backends support try-except.
> Think about ob-gnuplot or, say, ob-latex.

Indeed many do not. Defining some standard "features"
for org babel language implementations is something that
is definitely of interest so that we can provide clear interfaces
for things like stdio, error handling, return values, async,
file output, remote execution, sessions, return value caching,
module discovery/tangling, execution from file vs stdin, execution
without a file system path, runtime environment specification,
and much more. However, at the moment there is only a preliminary
survey of a subset of these that was put together by Ian Martins.

https://orgmode.org/worg/org-contrib/babel/languages/lang-compat.html

> the two could be unified if we expand the functionality of the async filter

While this might be possible, I would definitely hold off on this because
the changes in semantics absolutely will break many users' blocks. We
barely knew what the impact of changing the default return value for shell
blocks would be.

I absolutely look forward to the day when this can be done safely and
with confidence, but I think we need a much stronger handle on babel
interfaces in general before such a change could even be considered.

At the moment each ob lang impl pretty much has to be considered
to be completely unique, even if the text looks like bash for e.g.
shell, comint, and screen. Users are known to rely on undocumented
quirks of the ob lang impls that can differ wildly in their semantics.

Best!
Tom

next prev parent reply	other threads:[~2022-06-27 22:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-26  3:15 We have asynchronous sessions, why have anything else? Ivar Fredholm
2022-06-26  3:29 ` Ihor Radchenko
2022-06-26 19:20   ` Ivar Fredholm
2022-06-27  9:57     ` Ihor Radchenko
2022-06-27 22:04       ` Tom Gillespie [this message]
2022-06-28  0:41         ` Tim Cross
2022-06-28  1:15           ` John Kitchin
2022-07-06  1:41       ` Ivar Fredholm
2022-07-07 11:17         ` Ihor Radchenko

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='CA+G3_PMD+OdN1=yfR79aFaJFXrNzsAbX328JtOWer5jKO+98zw@mail.gmail.com' \
    --to=tgbugs@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=freddyholms@protonmail.com \
    --cc=ianxm@jhu.edu \
    --cc=yantar92@gmail.com \
    /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 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).