-
-
Notifications
You must be signed in to change notification settings - Fork 275
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
Support for plasticboy/vim-markdown #45
Comments
Thanks for your report 👍 |
Just confirming that I also am experiencing this behavior. Switching to a different colorscheme resolves the issue....whatever that is. |
I think you are correct about the "custom variable namespace". I looked through the repository OP linked to and in the
Anyway, not sure if that is a lot of work to implement but it would be really appreciated. |
I was able to get some basic highlighting working with the custom variable namespace. I added these lines at line 304 of It would be great to get more of this namespace mapped to nord because this seems to be a quite popular vim plugin (+2000 stars). Here is a link to the syntax file showing other regions that need to be mapped, https://github.com/plasticboy/vim-markdown/blob/master/syntax/markdown.vim
|
This adds support for the language plugin plasticboy/vim-markdown to match the style of the built-in markdown syntax styles. GH-45
@VVVFO @powelleric Sorry for the delay, unfortunately had not much free time to work on my projects. I've opened PR #57 which implements support for the plugin. It would be nice if you can test the changes and see if it works and you'd expect it to be highlighted. |
Justed tested, it worked perfectly! Thank you for your work @arcticicestudio ! |
…ort-plasticboy-vim-markdown Language plugin support for plasticboy/vim-markdown
The highlighting for Markdown will stop to work once 'plasticboy/vim-markdown' is installed. Could it be because they have a different system of syntax naming? I never had any Markdown highlighting problem with other color schemes before.
Expected:
Actual:
The text was updated successfully, but these errors were encountered: