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.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

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

What is the problem you're trying to solve?

I've noticed that I sometimes end up typing a bit too fast when adding white spaces in my code when I've recently used alt or option key + space in Mac in VS Code (for example when adding a $ for a variable), this results in non-breaking spaces (&nbsp) being added to the code which look identical to regular white spaces, but when parsed through sass