We’re rewarding the question askers & reputations are being recalculated! Read more.
2 replaced http://vi.stackexchange.com/ with https://vi.stackexchange.com/
source | link

Stumbled on the answer after some more searching:

syn region warning contains=Bad start="^not ok" end="^\ze[^#]"re=e-1,he=e-1

Had to slap a \ze in there. See http://vi.stackexchange.com/questions/398/can-vim-syntax-regions-be-made-to-touch-overlapCan vim syntax regions be made to touch/overlap? for reference.

Stumbled on the answer after some more searching:

syn region warning contains=Bad start="^not ok" end="^\ze[^#]"re=e-1,he=e-1

Had to slap a \ze in there. See http://vi.stackexchange.com/questions/398/can-vim-syntax-regions-be-made-to-touch-overlap for reference.

Stumbled on the answer after some more searching:

syn region warning contains=Bad start="^not ok" end="^\ze[^#]"re=e-1,he=e-1

Had to slap a \ze in there. See Can vim syntax regions be made to touch/overlap? for reference.

1
source | link

Stumbled on the answer after some more searching:

syn region warning contains=Bad start="^not ok" end="^\ze[^#]"re=e-1,he=e-1

Had to slap a \ze in there. See http://vi.stackexchange.com/questions/398/can-vim-syntax-regions-be-made-to-touch-overlap for reference.