Re: Feedback on Emacs-Jupyter

[Ken Mankoff <mankoff@gmail.com>]

Hi Nathaniel,

First, thank you (many times) for maintaining emacs-jupyter. It is one of the most-used tools on my computer. I've been using your software daily for the past few years to develop code and write papers.

I may think of more things as others reply, but the one thing I can think of now is that I sometimes have issues inputting tables into Python code blocks. We discussed this back in 2020/2021 here: https://github.com/nnicandro/emacs-jupyter/issues/267 It is not emacs-jupyter according to you, but I mention it here anyway.


Another feature that could be nice - Org has the ability to embed/encode images into the document (see https://emacs.stackexchange.com/questions/27060/embed-image-as-base64-on-html-export-from-orgmode and  http://mbork.pl/2017-12-04_Embedding_files_in_Org-mode ). I do not suggest doing this for large graphics, but for small graphics, it could be interesting to have a "* Graphics" section at the bottom where the encoded graphics are stored, and then display those encoded graphics at the normal location (#+RESULTS: blocks below the code or elsewhere if #+NAME'd).

Implementing this feature would mean you could have self-contained / single-file / standalone Org files with graphics, similar to how .ipynb files contain graphics within. I'm not sure how useful this would be, but I throw it out there as a concept/idea.

Thanks again for the excellent software,

  -k.


On 2022-01-04 at 15:24 -08, Nathaniel Nicandro <nathanielnicandro@gmail.com> wrote:
> Hello all,
>
> I'm the maintainer of the emacs-jupyter project
> (https://github.com/nnicandro/emacs-jupyter) which essentially
> integrates Jupyter kernels (https://jupyter.org) with Org mode source
> blocks.
>
> I wanted to make an introduction to the Org community. So...hello! And
> thanks for promoting the project on https://orgmode.org/features.html.
>
> I believe a lot of users of the project use it mainly for the Org
> integration. I thought it would be a good idea to get some feedback
> from the community on how their experience using emacs-jupyter has
> been. I'm getting back into active maintenance of the project and am
> looking for feedback to get a better idea of what the future of the
> project could look like. What features of standard Org source blocks
> do you find Jupyter source blocks are lacking? What potential features
> do you think would be useful for Jupyter source blocks to support,
> given the capabilities of Jupyter? What would it mean to see
> Emacs-Jupyter and Org more integrated? Of course, any other thoughts
> are welcome.