My first recommendation when writing AsciiDoc in VIM is to look elsewhere than the built-in syntax file. That syntax file is not great. It also doesn't recognize any of the enhancements that Asciidoctor introduces.
Thankfully, there are a lot of promising alternatives. One that comes to mind is https://github.com/dahu/vim-asciidoc. I'd really like to get some feedback about which plugin set works best, then add it as a recommendation on asciidoctor.org. We need to start pushing the VIM support for AsciiDoc forward more because it's kind of fragmented at the moment.
On Thu, Mar 10, 2016 at 1:40 PM, russurquhart1 [via Asciidoctor :: Discussion] <[hidden email]> wrote:
I know that there are a lot of people out there, like myself, that are writing asciidoctor files in vim.
I currently use the charon.vim color schemes that has been pretty good for most things, but some parts of it for asciidoctor files, using the latest asciidoc.vim syntax, just are kind of drab.
I was just curious if any of the vim asciidoctor writers could make any suggestions?
If you reply to this email, your message will be added to the discussion below:
On Thu, Mar 10, 2016 at 2:12 PM, russurquhart1 [via Asciidoctor :: Discussion] <[hidden email]> wrote:
So then, correct me if i am wrong, is that maybe some of the color schemes could better use features callled out in that syntax file?
My understanding about color schemes is that (like with syntax highlighters) they only focus on commonalities between languages. Since AsciiDoc is a markup language, there are a lot of structural elements that are not shared with programming languages (VIM's focus), so it's going to warrant customization. This is where it would be good to iterate in a dedicated repository instead of in VIM core.
To put it simpler, AsciiDoc has special requirements and we need to have color schemes configured specifically for that use case. The generic stuff just doesn't cut it.