i wanted to share that the syntax highlighting issues i and others have been having when editing markdown files are related to the runtime/syntax/markdown.vim natively bundled through vim and in this case neovim. I think this script interferes with a number of markdown syntax features for vim-markdown, and vim itself, such as spell Highlighting and so on. I wanted to bring it to your attention that you might want to include a note in the readme about disabling markdown.vim, if people notice buggy syntax highlighting. I initially thought vim-markdown could be responsible, but it is not.
my "solution" after a bit of various init.vim and ftplugin changes, was to edit the syntax/markdown.vim vim file to
finish
I tried to set b:current_syntax in init.vim and ftplugin/markdown.vim, neither of these seemed to do anything to prevent markdown.vim from executing. Any better suggestions than just terminating the "read-only" syntax file are welcome.
thank you for a great plugin.
this is a readme addition request.
i wanted to share that the syntax highlighting issues i and others have been having when editing markdown files are related to the
runtime/syntax/markdown.vimnatively bundled through vim and in this case neovim. I think this script interferes with a number of markdown syntax features for vim-markdown, and vim itself, such as spell Highlighting and so on. I wanted to bring it to your attention that you might want to include a note in the readme about disabling markdown.vim, if people notice buggy syntax highlighting. I initially thought vim-markdown could be responsible, but it is not.my "solution" after a bit of various init.vim and ftplugin changes, was to edit the syntax/markdown.vim vim file to
I tried to set
b:current_syntaxin init.vim and ftplugin/markdown.vim, neither of these seemed to do anything to prevent markdown.vim from executing. Any better suggestions than just terminating the "read-only" syntax file are welcome.