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

This is an issue in the markdown writer:

% pandoc -f native -s -t markdown
Pandoc (Meta {unMeta = fromList [("foo",MetaBool False)]})
[]
---
---

Bug Report

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

One of the best features of using SuperMemo for note taking is that there's peace in knowing no note will ever be permenantly forgotten as it will come back to you in time.

In Obsidian this is can be somewhat replicated using the 'Random Note' feature. Having this in Foam would be great. If this could include

Clearly describe the bug

::-moz-focus-inner is treated as a pseudo-class, not a pseudo-element, and so can cause false positives in no-descending-specificity.

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

no-descending-specificity

What code is needed to reproduce the bug?

a::-moz-focus-inner {}
a