+1 to this feature. In 2022 the answer was “it will be part of an upcoming major rework of the parser”… This is clearly not happening, would it be possible to just squeeze that one in the current setup? In the long run we’re all dead.
Buuuurmp
I don’t believe that impatience is of any use in the matter or cynicism increases the urge of those who are advancing the program to include this.
I would also like to see definition lists.
A plugin available for this is still very rudimentary, I was unable, to get it to work.
My last resort would be to program a plugin on my own. But that requires Electron, TypeScript and some other programming skills that I don’t have currently, which opens a time horizon …
Because of that, I am optimistic about future developments.
So for whatever reason I never saw/noticed this [!Note] syntax before and I just want to thank you (some 2.5 year later or so) for this - this may be my new favorite thing of the moment…
I agree with this in spirit, but I do worry - is maybe the reason they don’t allow parser plugins that it could be a security nightmare and or lead to super buggy / unpredictable results?
I know that when I was fiddling around with parsedown (a PHP Markdown parser) I did an extension of my own to plug in a couple features and I had to fight with it a bit to avoid causing really ugly downstream issues that tripped up the functionality - It turned out most of the issues were between the chair and keyboard, but It was monumentally easy for me to do dumb things and I wonder if the amount of effort to properly sandbox such a parser plugin architecure might be a bit high?
Honestly though yes I would love this - my first thought when reading through the request and the followups was “how come there haven’t been like 100 folks writing plugins that address this”
Yeah, I thought about doing this too, but it seems that for some reason, parser plugins specifically aren’t enabled/ possible? not sure I think perhaps there’s issues with how to do general enabling of folks to hook into the parsing in a way that doen’t seriously break other stuff?
I’ve not dug that far in. While I’m no stranger to JavaScript/Typescript, I’ve not really touched Electron on the coding side at all.
Another +1 for this feature
+1 here too, FWIW!
+1 Would also find definition lists very helpful, in many situations.