Unexpectedly disables Syntastic

[pasky]

Hi! I believe Eclim's current behavior of non-conditionally disabling Syntastic checking in some filetypes is bad. Basically, I would have expected that Eclim will disable Syntastic only at the point it is able to replace it, i.e. when eclimd is running and the project I'm editing is imported in Eclipse.

However, currently, if I'm using eclimd for working on big Java projects, it is unexpected that it spills over to editing isolated, unrelated C files. This seems to have bitten others that installed eclim and then were wondering why syntastic doesn't work.

Even if you figure out why Syntastic doesn't work on your files (which is really hard, eclim didn't come to my mind at all), the proper fix is non-obvious. I'd have expected let g:EclimCValidate = 0 to do the job, but it doesn't seem this option (or its Cpp, Html equivalents) has any effect at all...

[ervandew]

I would have expected that Eclim will disable Syntastic only at the point it is able to replace it, i.e. when eclimd is running and the project I'm editing is imported in Eclipse.

The problem is that syntastic, as far as I've seen, cannot be disabled on a per buffer basis, so eclim can either disable it completely for a filetype, or not at all. We may be able to use g:syntastic_ignore_files and have eclim add an entry for each eclim installed filetype and project combination. My only concern with doing that is I'm not sure how people may be manipulating that setting themselves and this could just be shifting issues from one group of users to another.

I'm open to concrete ideas on how to play nice with syntastic. I've only ever installed it long enough to add the disabling logic (and to refactor it once), so it would be great to have users that have incorporated syntastic into their workflow to decide how this should behave. @blueyed is the only other user that has provided real feedback in this regard.

This seems to have bitten others that installed eclim and then were wondering why syntastic doesn't work.

I can only think of maybe one or two cases of this being reported vs several cases of people reporting validation bugs that ended up being syntastic's vaildation and not eclim's, which was the only reason I started disabling syntastic for eclim supported filetypes.

I'd have expected let g:EclimCValidate = 0 to do the job, but it doesn't seem this option (or its Cpp, Html equivalents) has any effect at all...

That should work as long as you restart vim after adding it to your vimrc. Setting it manually in a running vim won't work if syntastic has already been disabled in the current vim instance.

[not-napoleon]

I was also bitten by this bug. I was editing a python file with eclim not running and trying to guess why I wasn't getting any syntax checking.