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

Bug Report

What happened?

incorrect markdown list display

Reproduce the Bug

- Test
    - + item
      + item
      + item

Expected Behavior

No response

Screenshots

Desktop Platform Information

Fedora Linux fc35.x86_64, Logseq 6.0.4

Mobile Platform In

• Foam version: v0.17.3
• Platform: Mac
• Issue occur on the foam template repo: Yes

Summary
When full path to repository contains parenthesis (e.g. My folder (1)), foam does not load the notes on start, which prevents link recognition, graph is empty, etc.

My best guess why that happens is that you use [micromatch library](https://www.

What steps are needed to reproduce the bug?

test.scss

$frames: ("one", "two", "three");

@each $name in $frames {
  @keyframes frame-#{$name} {
    /* CSS ... */
  }
}

$ npx stylelint test.scss

test.scss
 4:14  ✖  Expected keyframe name to be kebab-case  keyframes-name-pattern

The name is kebab case, but due to the string interpolation, the line is f

Currently, few icons are not visible in dark theme. Make them visible by using theme neutral icons. May be we can make use of https://shields.io/ to generate our own kind of badges. For eg: Javascript.

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