I have been reading #19 and perhaps a solution to that issue could be enough to make this integration happen.
Currently, in order to have a good notebook experience on neovim, you need two things: (1) a front-end translator which converts raw .ipynb files to a python/markdown file (example: jupytext), and (2) a back-end which interacts with jupyter to provide the runtime functionality (example: magma). At the moment, there is no integration between the two, so if I'm using jupytext magma does not recognise its cell format, for example.
Can something be done on this front to achieve a good notebook experience overall?
I have been reading #19 and perhaps a solution to that issue could be enough to make this integration happen.
Currently, in order to have a good notebook experience on neovim, you need two things: (1) a front-end translator which converts raw
.ipynb
files to a python/markdown file (example: jupytext), and (2) a back-end which interacts withjupyter
to provide the runtime functionality (example: magma). At the moment, there is no integration between the two, so if I'm using jupytext magma does not recognise its cell format, for example.Can something be done on this front to achieve a good notebook experience overall?
Thanks! Love the plugin!