Open Porges opened 7 years ago
I'm also not seeing the fenced code blocks (with tpope's version) get blacklisted. This might be complicated because it supports nested syntax highlighting in fenced code blocks. Should I open a separate issue for this?
The intent of the odd whitelisting was to allow for unfenced inline code examples such as this
to be wrapped via autoformat, or rather to avoid disabling of autoformat where they are present. But it's been a long time since I last visited that behavior. In addition, the syntax plugins may have changed to break the black/whitelists.
Attaching any examples to this issue that demonstrate undesirable behavior would be fine. I'll then try to reproduce in the next week or so. Thanks.
With tpope/vim-markdown, I think
markdownCodeBlock
should also be blacklisted.At the moment there is:
... so it looks like
markdownCodeBlock
would be blacklisted and then whitelisted again. Perhaps the blacklist should bemarkdownCodeBlock
and then the whitelist formarkdownCode
could be removed?