justinmk / vim-syntax-extra

Vim syntax highlighting for c, bison, flex

Vim syntax highlighting extras

A collection of syntax definitions not yet shipped with stock vim.

Bison, Flex

Authors:

• Panayiotis Karabassis
• Robert van Engelen

For:

• Bison - GNU parser generator
• flex: The Fast Lexical Analyzer
• RE/flex: advanced Flex++

Enhanced C definitions

Authors:

• Mikhail Wolfson, Helmut Schellong

Improved C syntax groups for operators, delimiters, user-defined functions, function calls, and a wealth of standard ANSI C function names.

Vim default	Enhanced

vim-syntax-extra's Issues

vim-syntax-extra seems very unhappy with my braces

Admittedly, I have a bit of an odd coding style, but even the more mundane things cause vim-syntax-extra to highlight my braces as if they were syntactically invalid:

const char * example [] = {
    [HL] = "Hello,",
    [WL] = "World!"
};

Noting that both HL and WL are validly defined in an enum earlier in the code, vim-syntax-extra still highlights both of these braces. There is no error output as far as I can see, but these braces are perfectly fine syntactically.

Problem with `{` inside a bison action

The following code is not highlighted properly:

i_bexpr : iexpr i_boolop iexpr
        { $$ = new Bool<int,int>(Bool<int,int>::Args{$1,$3},
                                 Bool<int,int>::T_ops{$2}); }
        | i_bexpr i_boolop iexpr
        { std::cout << $1->args[0]->repr() << std::endl;
          $1->args.insert($1->args.end(), $3);
          $1->ops.insert($1->ops.end(), $2);
          $$ = $1; }

It looks like that:

Thanks for these syntax files!

Rules with a '.' in the name are not colored

Hello

With a rule like

name.opt:
NAME
| OTHER
;

the coloring is not applied, because of the . in the name. As it is syntactically valid and not ambiguous (as far as I'm aware), it should be possible to correctly interpret it.

Braces color

Braces get marked as errors if I enable parenthesis recognition in the "delimiters"

cUserFunctionPointer does not highlight

However if I run this command to match it again

syn match cUserFunctionPointer "(\s*\*\s*\h\w*\s*)\(\s\|\n\)*(" contains=cDelimiter,cOperator

It starts working perfectly. But now, if I do

set ft=c

The highlighting disappears.

Syntax highlighting stops working

my syntax highlighting disappears after i have anything with brackets inside of a rule