minibufexpl.vim Highlight does not work anymore after switching to ad72976ca3df4585d49aa296799f14f3b34cf953

After pulling latest master from the repo, the syntax highliting for MBE stopped working. I was quite fond of this functionality...

The :syntax command run in MBE windows outputs: No Syntax items defined for this buffer I can see that the RenderSyntax is called, but the syntax seems to get cleared.

Regards: lukost

Aug 06 '13 08:08 lukost

Do you use your custom highlight setting? The name of the syntax highlight group has been changed in the last version, you might need to adjust you settings.

Aug 06 '13 13:08 weynhamz

I tried both: custom highlighting and vanilla config. Nothing works for me.

As I've stated before, the MBE window does not have any syntax defined (calling 'syntax' in MBE window gives: "No syntax items defined for this buffer"). I can manually (copy-paste or source) the <SID>RenderSyntax and then everything works just fine.

btw thanks for quick answer.

Aug 07 '13 17:08 lukost

Do you have 'g:did_minibufexplorer_syntax_inits' defined somewhere in your configuration?

Aug 08 '13 05:08 weynhamz

No, I don't.

Aug 08 '13 07:08 lukost

I have solved the problem by adding 'syntax' folder into the plugin dir, and placing minibufexpl.vim file in it. The content is taken from RenderSyntax:

syn match MBENormal                   '\[[^\]]*\]'
syn match MBEChanged                  '\[[^\]]*\]+'
syn match MBEVisibleNormal            '\[[^\]]*\]\*'
syn match MBEVisibleChanged           '\[[^\]]*\]\*+'
syn match MBEVisibleActiveNormal      '\[[^\]]*\]\*!'
syn match MBEVisibleActiveChanged     '\[[^\]]*\]\*+!'

The RenderSyntax seems to be called in wrong window... Have you thought about moving the actual syntax into syntax file instead of defining it inline?

This seems to fix the problem.

Aug 08 '13 07:08 lukost

Sorry for closing and reopening - my daughter was playing with the mouse...

Aug 08 '13 08:08 lukost