From: Nathaniel Nicandro <nathanielnicandro@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Feedback on Emacs-Jupyter
Date: Thu, 13 Jan 2022 14:56:57 -0600 [thread overview]
Message-ID: <87czkvz1ts.fsf@gmail.com> (raw)
In-Reply-To: <87ilupoznn.fsf@localhost>
> Thanks a lot for your work!
Thanks a lot for maintaining the wonderful Org package!
> Hope it helps.
Thanks, I've previously seen the video and it does help with figuring
out the issues with emacs-jupyter as it currently stands.
> Also, it appears that Jupyter is getting a lot of traction in research
> community and it is distributed via GPL-compatible license (modified BSD
> license). I believe that we should consider including the Org-related
> part to Org core if the rest can be distributed via ELPA. WDYT?
I would be happy to contribute the Org related parts of emacs-jupyter to
Org core. I think that would mainly mean the ob-jupyter.el file that is
similar to the other ob-*.el files. How would I go about contributing
ob-jupyter.el in this specific situation?
With regards to distributing the rest via ELPA, I would like to get the
code base into a more stable state as I am planning to integrate changes
that I've been working on this past year which may cause some breaking
changes in people's configs. Once I've shaken out the bugs after I merge
those changes, I'll be more than willing to submit emacs-jupyter as an
ELPA package, if they would have it.
Regards,
--
Nathaniel
next prev parent reply other threads:[~2022-01-13 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 23:24 Feedback on Emacs-Jupyter Nathaniel Nicandro
2022-01-05 4:37 ` Ken Mankoff
2022-01-06 18:44 ` Nathaniel Nicandro
2022-01-05 7:26 ` Colin Baxter 😺
2022-01-05 17:39 ` David Dynerman
2022-01-07 18:57 ` Nathaniel Nicandro
2022-01-08 11:27 ` Daniel Fleischer
2022-01-12 13:24 ` Ihor Radchenko
2022-01-13 20:56 ` Nathaniel Nicandro [this message]
2022-01-14 14:25 ` 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=87czkvz1ts.fsf@gmail.com \
--to=nathanielnicandro@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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
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).