[Feature Request] Export outputs to .ipynb files about molten-nvim HOT 4 CLOSED

This would be awesome. I can't offer a lot, but as far as matching cells goes, could potentially just rely on using markdown. Use code-blocks to define cells and the space between code blocks to define markdown-cells.

from molten-nvim.

@SigmaRichards Ideally this should work without relying on the file format. There are many ways that people convert ipynb to plaintext. The most common are Quarto and Jupytext. Quarto converts to a markdown-esque format. Jupytext can convert to either a .py file with comments delimiting cells, or a plain markdown file.

There are also other ways that people create notebook-like files, neorg and NotebookNavigator.nvim off the top of my head, both of those delimit cells in different ways.

I'd like for all of these methods to work with this command.

I also want to make clear that this wouldn't be converting markdown to ipynb, which is a solved problem as far as I'm concerned. This would just be a way to add the outputs from molten to an existing, corresponding, ipynb file.

from molten-nvim.

I'm also like 85% sure that just relying on the cell order in the file (in addition to the code content) will be enough to not confuse different cells

from molten-nvim.

@SigmaRichards feel free to checkout that PR, it's in a working state rn. simple instructions for testing: take a jupyter notebook file, convert it to a plaintext format however you want (make sure they have the same name, ie. test.ipynb and test.qmd) and then open the plaintext doc, run code with molten, and run :MoltenExport.

You can then open a copy of the notebook file that was produced in jupyter-lab and see the output from the code you ran.

Keep in mind that things might break and I haven't extensively tested yet, if you find issues you can leave them here and I can be sure to iron them out!

from molten-nvim.