bfrg

There's also [vim-projectionist](https://github.com/tpope/vim-projectionist/) where you can define alternate files, like source and header files (among many other things).

Yes it is mentioned in `jq --help` (and also in the online manual), but it is **not** mentioned in `man jq`.

@anntzer I gave up on such complicated syntax highlighting long time ago. I didn't really need it anyway. Have you tried [color_coded](https://github.com/jeaye/color_coded)?

There's [YCM-Generator](https://github.com/rdnetto/YCM-Generator) that also generates `.color_coded` files.

Have you looked at the alternatives [clighter8](https://github.com/bbchung/clighter8) or [chromatica.nvim](https://github.com/arakashic/chromatica.nvim)? Both are written in python. There is also [taghighlight](https://github.com/kendling/taghighlight), which highlights keywords based on a ctags file.

I am not completely against it, but with Vim's currently shipped [c.vim](https://github.com/vim/vim/blob/67fbdfefd26a237831c3838f799d3e6198c8a34a/runtime/syntax/c.vim) syntax file it just won't work most of the time. What you asked for could be accomplished with...

Thanks for reporting this. The regex for highlighting function names is very simple. Just highlight all words appearing before an opening parenthesis. I don't know if I want to make...

@oblitum Which font size is that in the first picture? Terminus at 12 looks fine (_left:_ 11, _right:_ 12):  When you look at the numbers in the status line...

@Piping Just FYI (not trying to be Mr. Smarty pants here), the right way to set `formatprg`, or any other filetype-specific options, is either through `autocmd` in your `vimrc`: ```vim...

Have you tried the `-i, --show-info` option?