Code cells that do not produce output, e.g. python import statements are not considered as code cells when importing outputs.
As a consequence :MoltenReevaluateCell/All fails unexpectedly after importing output from an ipynb file.
The fix for this issue comes with a new feature. There's a new output status NEW. New cells have no output, and have never been run (execution count == null), currently they're only created by the :MoltenImportOutput command, and they show Out[_]: Never Run in virtual text or the floating window.
The import script no longer breaks on cells that have a 0 length output list, and instead will create a molten cell, marked either DONE or NEW based on the exec count.
If someone has a more concise or otherwise better way to communicate Never Run I'd love suggestions. I personally don't like the text Never Run but need something to be there.
supersedes #221
Code cells that do not produce output, e.g. python import statements are not considered as code cells when importing outputs.
As a consequence
:MoltenReevaluateCell/All
fails unexpectedly after importing output from an ipynb file.The fix for this issue comes with a new feature. There's a new output status
NEW
. New cells have no output, and have never been run (execution count == null), currently they're only created by the:MoltenImportOutput
command, and they showOut[_]: Never Run
in virtual text or the floating window.The import script no longer breaks on cells that have a 0 length output list, and instead will create a molten cell, marked either
DONE
orNEW
based on the exec count.If someone has a more concise or otherwise better way to communicate
Never Run
I'd love suggestions. I personally don't like the textNever Run
but need something to be there.