diff options
| author | Marco Hinz <mh.codebro@gmail.com> | 2016-12-09 19:54:24 +0100 | 
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-12-09 19:54:24 +0100 | 
| commit | 5082af415f762e5f5974214e32deff883141bfc2 (patch) | |
| tree | aaa6568a79e2d920b53bf3de827adde8959572de /runtime/syntax/kscript.vim | |
| parent | 7da7ff7c5c79dd36e053f5b5e86046838445bb8e (diff) | |
| download | rneovim-5082af415f762e5f5974214e32deff883141bfc2.tar.gz rneovim-5082af415f762e5f5974214e32deff883141bfc2.tar.bz2 rneovim-5082af415f762e5f5974214e32deff883141bfc2.zip | |
Health: rework syntax (#5744)
- By re-enabling code blocks (every line that doesn't begin with a "-" and is
  indented by at least 4 spaces), we prevent the Markdown syntax to evaluate "_"
  as beginning for italic text.
  That's the case for `:CheckHealth deoplete` for instance. It would output:
    $ cat /tmp/log_{PID}
  Since the deoplete check gets run first, almost all of the following
  `:CheckHealth` output would be italic.
- Since we re-enable code blocks, we now have to tell our custom syntax that it
  can be part of markdownCodeBlock as well. Otherwise there would be no
  highlithing for our keywords ERROR, INFO, etc. after 4 spaces of indent.
- Since we do the above anyway, we make it work for mkdListItemLine as well.
  That's a highlight group from `plasticboy/vim-markdown` opposed to the shipped
  markdown syntax (which essentially is `tpope/vim-markdown`). Before this patch
  there was no highlighting at all in the `:CheckHealth` output.
Diffstat (limited to 'runtime/syntax/kscript.vim')
0 files changed, 0 insertions, 0 deletions
