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

• Foam version: 0.9.1
• Platform: Mac
• Issue occur on the foam template repo: Yes

Summary
Having a folder named with a name ending in .md results in:

An error occurred while bootstrapping Foam. Error: EISDIR: illegal operation on a directory, read

Steps to reproduce

1. Name a folder with a name ending in .md
2. Clo

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

Clearly describe the bug

declaration-property-unit-allowed-list trips on SCSS function contents. Specifically color functions, which it should ignore.

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

declaration-property-unit-allowed-list

What code is needed to reproduce the bug?

$input-border: #639;

button {
  border: 1px solid lighten($input-border, 20%);
}