Undefined variable: main_syntax

[danbruegge]

Hi, after some months not using haxe. I try to start a new project.

I moved from vim to neovim. Reinstalled vaxe and every start of neovim with a haxe file will show this errors:

My nvimrc settings for vaxe:

let g:vaxe_cache_server = 1
let g:vaxe_lime_target = "linux -neko -64"

Regards, Dan

[danbruegge]

push. no one can help?

[jdonaldson]

I've been on vacations, I'll check into this soon.

On Sunday, December 6, 2015, Daniel Brüggemann notifications@github.com
wrote:

push. no one can help?

—
Reply to this email directly or view it on GitHub
#85 (comment).

[danbruegge]

Thanks. :)

Update:
Hah, i solved it by my own. 👍

I also use vim-plug to manage my plugins. There is an option where you can limit the plugin to a specific filetype. For vaxe i'll do the same like: Plug 'jdonaldson/vaxe', { 'for': 'haxe' } and it turns out, that this was the Problem. I think vim-plug loads vaxe to late. After loading the second file all works as expected.

Now i've only: Plug 'jdonaldson/vaxe' and vaxe is working fine from the start.

[danbruegge]

Solved in a0f8b4d

Thanks. :)

[jdonaldson]

You're very welcome. Good to know this is working for neovim, I'm going to start using that more.

[danbruegge]

:) Currently i tested it only on my machine on work, where i don't use haxe. So i only touched a new file and opened with nvim. On the evening i'll test it also @home.

[danbruegge]

Ok, problem still existis, if i use vaxe with Plug 'jdonaldson/vaxe', { 'for': 'haxe' }.

It disappears if i use the plugin with Plug 'jdonaldson/vaxe'

So, i think i should add something extra to the for but i don't know what.

[jdonaldson]

the "for" designation in the Plug config is a bit nonstandard. My guess is that it is preventing some of the global vaxe config logic from working. Vaxe works on hxml, hx, and hss, as well as providing some project-specific functionality (e.g. it tries to see if you are working on an openfl project). So, it is doing useful things even if you're not working on an hx file. I should mention that I took care for it not to add significant overhead for non-haxe development, so there's really no reason to prevent it from loading and running normally.

[danbruegge]

Ok, thanks for the info. :)