Closed chocolateboy closed 10 years ago
Interesting... I don't have such a problem neither on Ubuntu nor on OS X. Do you have any specific configuration options that may cause this, e.g. a non-default 'magic' value? Does it reproduce on a clean (no .vimrc) setup?
Do you have any specific configuration options that may cause this, e.g. a non-default 'magic' value?
Not that I'm aware of. vim -u NONE
was the first thing I tried. The problem doesn't exist for me prior to this commit, and it goes away if I replace contains=ktComment,ktTodo,@Spell
with contains=ktTodo,@Spell
.
Does this also fix something? :)
No, it's just for consistency :-)
I can't reproduce the main issue with vim 7.3.409 (though it still barfs on /*/**/*/
and /* */*
without this patch). My 7.4 patchlevel is 52.
Thank you!
The whole of the following program is highlighted as a comment for me in vim 7.4 (Ubuntu 14.04):
The problem appears to be that
/*
is matched as the start of the inner/contained region rather than the start of the outer/containing region i.e. this works:The documentation doesn't help much, but using a
matchgroup
(and not giving it the same name as the region) seems to solve the problem, and even handles/*/**/*/
and/* */*
(via) correctly.I also updated the README to include Vundle and Pathogen installation instructions.