nvim-ipy VS jupytext.vim

In my setup the figures appear as new windows on my other monitor, which works really well. If you want to display the figures inline, you can for example use QtConsole. You would then need another plugin to connect vim and IPython, for example vim-ipython (no support for cells as far as I know) or nvim-ipy (for neovim). Here's an article that describes a setup with the latter: https://www.blog.gambitaccepted.com/2020/04/26/neovim-qtconsole-setup/

There's also nvim-ipy (but I don't use neovim, so I can't recommend it).

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.