From: Jack Kamm <jackkamm@gmail.com>
To: Timothy <tecosaur@gmail.com>, Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Async session eval (2nd attempt)
Date: Sun, 25 Apr 2021 00:05:50 -0700 [thread overview]
Message-ID: <874kfudesx.fsf@gmail.com> (raw)
In-Reply-To: <877dkqx4kn.fsf@gmail.com>
Hi Timothy,
> This is moving at a glacial pace, but I'd love to see this merged ---
> there's clearly a lot of interest in this from the community if not
> within this mailing list (ob-async which is more limited has 250 stars
> on GitHub).
Yes, this has taken far too long -- sorry about that.
There have been a few things going on in my life recently, among them a job change. I am in the process of trying to get my FSF copyright forms approved at my new job. I think this will eventually happen, but the process is moving slowly.
My last update on this thread was shortly before changing jobs, and I decided not to merge until I was sure I'd be able to stick around to maintain it.
If someone is willing to apply the final tweaks and help with maintenance of this functionality, please go ahead and merge this in. Otherwise, I'll merge this as soon as I've got my paperwork approved and am back in action.
Jack
next prev parent reply other threads:[~2021-04-25 7:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 18:54 [PATCH] Async session eval (2nd attempt) Jack Kamm
2020-10-26 2:23 ` stardiviner
2020-10-26 9:46 ` Eric S Fraga
2020-11-09 4:09 ` Kyle Meyer
2021-01-03 8:51 ` TEC
2021-02-28 22:23 ` Jack Kamm
2021-03-01 6:22 ` Timothy
2021-03-04 5:13 ` Kyle Meyer
2021-04-25 6:26 ` Timothy
2021-04-25 7:05 ` Jack Kamm [this message]
2021-04-25 12:40 ` ian martins
2021-05-18 16:18 ` Jack Kamm
2021-04-25 14:39 ` Bastien
2021-05-15 21:09 ` Bastien
2021-05-18 16:15 ` Jack Kamm
2021-05-18 16:20 ` Jack Kamm
2021-05-19 9:01 ` Bastien
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=874kfudesx.fsf@gmail.com \
--to=jackkamm@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.com \
--cc=tecosaur@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
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).