-
Notifications
You must be signed in to change notification settings - Fork 10
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
Markdown backend: complete implementation #35
Conversation
…lly foldable trees Currently, multiline preformatted content as separate inline code markers. Will consider using code blocks...
First experiments with
|
Preformatted code is still broken.
Will add configuration and tune the table output next. Maybe the html table conversion could be better too.
…hen not inline (uses multiline heuristic when adding frames), use `div` instead of `span` when not inline.
Let me know if you'd like to have
So, I noticed I get a lot of fluff because I've used |
I checked that GitHub's Markdown rendering is capped at below 2MB. VSCode Markdown rendering works with bigger files, but there's an annoying waiting period (in that there's no reaction, a progress indicator would make it more bearable) that's even longer than with GitHub. |
I'll implement this simple case, since |
Complement of `multiline_heuristic` is the domain of `line_of_length`.
optimally escape all Markdown constructs (i.e. only when needed), minimize the use of ` ` -- but a slight temporary regression, needs `white-space: pre`.
…`Code_quote` `Code_quote` now uses a middle-dot to break whitespace collapse, including in the indentation.
Unfortunately, it seems inside `style="white-space: pre"` Markdown is not processed?
Note: without it, HTML collapses regular and nbsp spaces -- follow up.
` ` is unreadable and collapsed with surrounding spaces.
(since it doesn't pick up styles from <span>).
This reverts commit 9fd1686.
The biggest bummer is that GitHub Markdown rendering, as far as I see, just entirely rejects using styles provided by |
on Markdown table header lengths.
Currently, multiline preformatted content as separate inline code markers. Will consider using code blocks...
I'll also test links, complex combinations and big output sizes.