emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Ivar Fredholm <freddyholms@protonmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
	"bzg@bzg.fr" <bzg@bzg.fr>
Subject: Re: We have asynchronous sessions, why have anything else?
Date: Thu, 07 Jul 2022 19:17:26 +0800	[thread overview]
Message-ID: <87h73tuq7t.fsf@localhost> (raw)
In-Reply-To: <ft3mszm9kzLQP17TveEqAxqDtNTVhJuD9JYgBUV53OaB1rAmA0ghOWMuElqa5vxOR3q3u7JVlh_9uMwk2pZMvW2ozQLRbmSYjhyaunGw4HE=@protonmail.com>

Ivar Fredholm <freddyholms@protonmail.com> writes:

> Hi Ihor, I have a prototype of what I mentioned earlier, at least for python. This supports asynchronous, synchronous, session, and session-less blocks. It's pretty messy but it helps to illustrate what I had in mind. Let me know what you think.

I am not sure how I feel about it.
From cursory look, the idea looks reasonable implementation-wise.

However, there is one big important requirement which does not appear to
be obeyed by your code: We _must_ be backwards-compatible. All the
existing babel backends must not be broken, especially third-party ones.
We must not make breaking changes to non-private function definitions.

Also, I do not see error handling as it is implemented in our current
babel code: Errors should be displayed in a popup buffer.

Best,
Ihor


      reply	other threads:[~2022-07-07 11:17 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
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 [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 \
    --in-reply-to=87h73tuq7t.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=bzg@bzg.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=freddyholms@protonmail.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
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

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