You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, notebooks are converted into a long Markdown document, where Jupyter code cells are simply rendered as markdown code blocks. However, this means that if a markdown cell contains a code block, this code block is indistinguishable from a Jupyter code cell. There are several possible approaches to solve this issue:
we could simply indent markdown code blocks by a small amount. this would be the simplest solution.
we could modify the notebook rendering process to factor in the ideas of Jupyter "cells" - this way, we could additionally do things like adding the cell number on the left (idk what it's called, basically the execution order thing tho), or being able to collapse the output as you would in an actual Jupyter notebook.
duanwilliam
changed the title
Distinguish between markdown cell code blocks and Jupyter notebook code cells
[website] Distinguish between markdown cell code blocks and Jupyter notebook code cells
Apr 21, 2022
I think the execution order would be nice but not necessary. And it would be nice to be able to collapse code output (especially if it's super long and we only want to either show none of it or last 20 lines or something)
Currently, notebooks are converted into a long Markdown document, where Jupyter code cells are simply rendered as markdown code blocks. However, this means that if a markdown cell contains a code block, this code block is indistinguishable from a Jupyter code cell. There are several possible approaches to solve this issue:
we could simply indent markdown code blocks by a small amount. this would be the simplest solution.
we could modify the notebook rendering process to factor in the ideas of Jupyter "cells" - this way, we could additionally do things like adding the cell number on the left (idk what it's called, basically the execution order thing tho), or being able to collapse the output as you would in an actual Jupyter notebook.
cc @StoneT2000 what are your thoughts?
The text was updated successfully, but these errors were encountered: