Invalid $VIM breaks JavaSearch, completion.

[Ryan Betts]

All,

I recently installed eclim - pretty awesome. A clever hack! Thank you
for taking the time to provide useful documentation and list responses
- very helpful in getting started.

I would like to log one (self-inflicted) problem to the googleverse. I
initially had the $VIM environment variable set to /usr/bin/gvim, not
realizing this variable had meaning to VIM. (At least in Ubuntu
9.04's default vim/gvim packages.)

This causes eclim to fail JavaSearch, Validate, java completion, etc.
with errors like "E492: Not an editor command: JavaSearch" and "E764:
Option 'completefunc' is not set", while succeeding at EclimValidate,
PingEclim, ProjectCreate, ProjectInfo, ProjectTree and even
ProjectProblems.

Unsetting $VIM resolved this issue.

(I'm a novice vim user, in case my naiveté with regards to $VIM needs
explanation :-))

Thanks for eclim,
*--Ryan.

[Eric Van Dewoestine]

On Sun, Dec 06, 2009 at 07:53:07AM -0500, Ryan Betts wrote:
> All,
>
> I recently installed eclim - pretty awesome. A clever hack! Thank you
> for taking the time to provide useful documentation and list responses
> - very helpful in getting started.
>
> I would like to log one (self-inflicted) problem to the googleverse. I
> initially had the $VIM environment variable set to /usr/bin/gvim, not
> realizing this variable had meaning to VIM. (At least in Ubuntu
> 9.04's default vim/gvim packages.)
>
> This causes eclim to fail JavaSearch, Validate, java completion, etc.
> with errors like "E492: Not an editor command: JavaSearch" and "E764:
> Option 'completefunc' is not set", while succeeding at EclimValidate,
> PingEclim, ProjectCreate, ProjectInfo, ProjectTree and even
> ProjectProblems.
>
> Unsetting $VIM resolved this issue.

Interesting. I'm surprised that vim didn't just override your value.
I may have to see if there is a way for eclim to detect this issue.

> (I'm a novice vim user, in case my naivet� with regards to $VIM needs
> explanation :-))

The vim help has some docs on $VIM:
:h $VIM


Thank you for posting about this. This issue probably would have been
very difficult for me to help you diagnose, so I'm glad to see that
you were able to figure it out.

--
eric