Peter Hodge wrote: > Thanks for your help, I had another look and found out you need another syntax > command to reproduce it properly. Here is the revised bug report > > Start vim using > > vim -u NONE > > insert the following test code (note that the 4th line must be indented). > > array($foo) > is_array $foo > is_array($foo) > is_array($foo) > > Apply the following syntax commands: > > syn on > syn keyword Function is_array > syn region r1 matchgroup=Type start=/array(/ end=/)/ > syn keyword Error foo containedin=NOTHING > > You will find that the keyword is_array and region r1 are confused > over how to highlight is_array(...) when it doesn't start at the > beginning of the line, and it has something to do with the 'foo' > keyword having a 'containedin=' option.
I can reproduce the problem. Indeed looks like a bug. Removing "containedin=NOTHING" solves it, while it should not change anything. -- hundred-and-one symptoms of being an internet addict: 10. And even your night dreams are in HTML. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
