-
-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ox-ipynb does not always preserve org subtrees using Markdown headings #47
Comments
It also might make sense to put headings for each subtree to a separate cell in notebook, as Collapsible headings (https://github.com/ipython-contrib/jupyter_contrib_nbextensions/tree/master/src/jupyter_contrib_nbextensions/nbextensions/collapsible_headings) extension does not work great with the way headings get exported at the moment. |
This allows them to become collapsible.
I cannot reproduce the first comment, for me the headings are preserved. The collapsible headings is a nice idea. I have implemented that I think. That raises the notebook up to 1.1% of the goodness of org-mode ;) |
I cannot reproduce the heading promotion problem described in the first comment either. However, with f9c485e I'm getting two cases where specious markdown cells are inserted. I think I've narrowed them to these conditions, but someone should try to reproduce:
Also, +1 adding this. I haven't used nbextensions yet, but they look intriguing... |
Those are both issues. I think I fixed them both. thanks for testing them out! |
btw, the collapsible headings makes big notebooks much more usable! |
Export for one of the large-ish org files I was working with recently stopped working after the change. This is the exception I get
|
I guess that is happening from s-trim(nil) somewhere. If you can get a small working example it is probably easy to fix. I can't reproduce it on the ones I have tried so far though. |
Closing this until a small example that reproduces the issue can be made. |
Hi John, I just discovered that there are cases when level of nesting is not being preserved with Markdown headings - often a block that was a subtree in org file, becomes a H1 heading in Markdown.
The simplest example I could come up with would be content below, if you were to export it, are not preserved will become H1 heading instead of H2.
The text was updated successfully, but these errors were encountered: