magma-nvim VS jupytext.vim

You use magma-nvim for interactive jupyter experience (or my fork which also includes three last PRs)

FYSA: https://github.com/dccsillag/magma-nvim & https://gitlab.com/usmcamp0811/nvim-julia-autotest

Check out Magma.. it works with Julia.. see my open PR for examples... does require IJulia.

Just throwing this out there... cause its pretty cool!! https://github.com/dccsillag/magma-nvim

I use them all the time and there are many features that differentiates it from vim, which is why I asked for clarification. In any case this plugin is pretty sweet if you want to evaluate cells within vim: https://github.com/dccsillag/magma-nvim

Have you taken a look at https://github.com/dccsillag/magma-nvim?

My current workflow is a combined version of Maxwellrules' solution and magma.nvim. I am mostly satisfied. I could maybe use vim-jukit's cell division, but otherwise I am good for now. Though again: I am definitely open for better solutions.

You can check out https://github.com/dccsillag/magma-nvim A nice, integrated solution in my opinion.

I tried plugins like jupytext.vim but it was not enough mature in these old times :-)

You can also use jupytext.vim to easily open and edit notebooks. Then you can use a REPL program to evaluate the different cells individually. The only downside to me is that you can’t save the output back to the notebook (images etc.).

Editing *.ipynb files can also be edited with jupytext.vim, which automatically converts *.ipynb files using jupytext which you open them in Vim. I haven't tried this yet (it's on my todo list), but it looks pretty solid.

For editing notebooks in vim, I've created https://github.com/goerz/jupytext.vim. Note that this does not allow to run any cells, it just edits the inputs.

The motivation behind this was to have some basic interaction with existing ipynb files on a remote server without having to run the jupyter server (and set up port forwarding etc.) It's worth noting that the `jupytext.vim plugin is most useful if you're actually not running `jupytext` within jupyter; If you are, you could just directly open the .py or .md files linked to any .ipynb in your editor.

I've used `jupytext.vim` to edit existing notebooks and then run them through `jupyter nbconvert --to notebook --execute`. It's also great for refactoring: moving code from a notebook files into a module, between notebooks, or to create a new notebook as a variation of an existing one.