-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: support fenced div blocks #236
Comments
I'm going to say this is more than a feature request: this is a basic bit of Pandoc's syntax that differs from regular Markdown syntax and using it blows the highlighting to bits without a workaround. Even if we don't do anything super special with the blocks, using them shouldn't break the plugin. |
See also jgm/pandoc#5461. |
Workaround for vim-pandoc#236. Make sure that the colon isn't followed by additional colons the same way we already do for tildes.
Workaround for #236. Make sure that the colon isn't followed by additional colons the same way we already do for tildes.
Does the code below work? I added it to syntax/rmd.vim and didn't note any side effects yet. syn match pandocDivBegin '^:::\+ {.\{-}}' contains=pandocHeaderAttr
syn match pandocDivEnd '^:::\+$'
hi def link pandocDivBegin Delimiter
hi def link pandocDivEnd Delimiter |
Hi,
Pandoc supports fenced DIV blocks after v2.0. The syntax highlight conflicts with definition lists. As a workaround, I set
use_definition_lists = 0
to render fenced_divs correctly.Please consider implementing this syntax into this awesome plugin :)
The text was updated successfully, but these errors were encountered: