What pain point are you perceiving?.
I'm reviewing Marked documentation, attempting to create a custom setup where, it transforms new lines starting with 'notice: ' into a specifically formatted DIV. By my understanding I need to first add a custom named tokenizer and then a renderer based on it? Or am I going about this the wrong way?

Describe the solution you'd like
I'd like to ea

Pandoc version: 2.12

Also behaves this way on https://pandoc.org/try/?text=***+Level+3%0A****+Level+4%0A%0A&from=org&to=org&standalone=0

Bug Report

• Foam version: 0.7.7
• Platform: Windows
• Issue occur on the foam template repo: Yes

Summary
When using full numeric tags (#2021), those get correctly highlighted in VSCode but don't get listed on tag explorer

Steps to reproduce

1. Edit any markdown document inside Foam with a numeric tag (#2021)
2. Save file, and check tag explor

Clearly describe the bug

Getting selector-class-pattern violations on LESS mixin definitions.

Which rule, if any, is the bug related to?

selector-class-pattern

What code is needed to reproduce the bug?

.my-mixin(@x: 5) {
  line-height: @x;
}

What stylelint configuration is needed to r

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