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
I have this .ipymd notebook with a simple one-line, long header:
# This is an example of a long header, with many, many words. This really is an example of a long header, with many, many words.
notedown incorrectly produces the following Markdown:
# # This is an example of a long header, with many, many words. This really
is an example of a long header, with many, many words.
I see two problems:
Big problem: there should be not line break (after "This really").
The (say HTML) rendered output should not show "# This is an example…" but "This is an example…", like in the notebook, right?
I could not find where in the code the header is broken.
More generally, the Markdown from Markdown cells should probably be left untouched too, no?
The text was updated successfully, but these errors were encountered:
lebigot
changed the title
Markdown header is incorrectly broken into multiple lines
Markdown header is incorrectly broken into multiple lines (and displayed strangely)
Aug 28, 2018
This happens with every long line, not just headers.
I am also looking for a solution to this issue.
Meanwhile, @lebigot , you can use html syntax as a workaround. <h3> this very long title will not be incorrectly broken into multiple lines, even if it is very very long.</h3>
I have this .ipymd notebook with a simple one-line, long header:
# This is an example of a long header, with many, many words. This really is an example of a long header, with many, many words.
notedown incorrectly produces the following Markdown:
# # This is an example of a long header, with many, many words. This really
is an example of a long header, with many, many words.
I see two problems:
I could not find where in the code the header is broken.
More generally, the Markdown from Markdown cells should probably be left untouched too, no?
The text was updated successfully, but these errors were encountered: