Markdown

Marked version:
3.x.x

Describe the bug
A clear and concise description of what the bug is.

Right now, import {use} from "markedjs" does not work, this worked in 2.x.x.

To Reproduce
Steps to reproduce the behavior:

Install & import it.
The DefinitelyTyped definitions also mark this incorrectly as being supported still.

A workaround is importing one of the structur

Explain the problem.

Converting the following:

pandoc -f gfm -t asciidoctor <<EOF
- [ ] a
- [x] b
EOF

produces:

* ☐ a
* ☒ b

instead of using the checklist syntax (see asciidoctor docs):

* [ ] a
* [x] b

This seems related to [the recently fixed org-mode r

Feature request

Apologies if this is already a thing, but I couldn't find any informat

Currently embedding includes the note/section content inlined.

It would interesting to support different "embed styles" to customize the embedding behavior with:

• inline (include the full section, title included, in the note)
• content (include the full section, excluding the title, in the note)
• card/panel (add the embed inside a card or panel)

This could either be set by a workspace

Describe the bug

To Reproduce
Steps to reproduce the behavior:
input {{query (page-tags myblog)}}

Expected behavior
Don't show block

Screenshots

Desktop (please complete the following information):

• OS: [win10
• Version [0.2.10]

What is the problem you're trying to solve?

I guess that selector-max-universal is performance related rule.
I.e. it is supposed to forbid patterns that hit perfomance.

Consider the following patterns (with selector-max-universal = 1):

1. "*" involves O(N) search. So, it is Good.
2. "* *" involves O(N^2) search. So, it is Bad.
3. "* + *" involves O(N) search ("+ *" = next element = it

I'd like there to be an option to have code blocks be line wrapped. Maybe a check box for it in Rendering -> "Syntax highlighted code block" next to "Show line numbers" etc.?

If I try hard enough I can dig through the css files in Contents/Resources/Prism/themes and change "white-space: pre;" to "white-space: pre-wrap;", but doing so breaks the code signature of the app. And that's not a very n