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

The table ID is currently lost, but could be included by wrapping the table in a bookmark (probably via empty paragraphs before and after the table).

Bug Report

Some ideas to support easier and more controllable tag management:

• auto-complete/intellisense for tags. if we consider that they are to be in some way controlled or loosely controlled it would be helpful.
• an ability to dump all tags in the alphabetical order into an auto-updated md file for easy viewing, exporting, visualization, etc...

What is the problem you're trying to solve?

I want to ignore only specific pseudo classes. In Angular its very common to use :host pseudo class, so this always takes 1 place in calculating nested depth

What solution would you like to see?

rules: {
    'max-nesting-depth': [
        1,
        {
            ignoreAtRules: [':host'],
        },
    ],
},

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