On Fri, Dec 04, 2009 at 09:39:22AM -0800, Michael Scheper wrote:
> G'day people,
>
> I'm using eclim for the first time and I'm really impressed—this will
> transform the way I code as much as when I started using vim 15 years
> ago. However, :ProjectGrep doesn't seem to work for me. e.g: in vim,
> with eclim otherwise working, if I type the command:
>
> :ProjectGrep/foo/*.java
>
> it says 'No results found', even though I know that string exists in
> my project. Since I'm not sure sure whether the 'file pattern' is
> meant to be a regex or a filespec, I've also tried :ProjectGrep/foo/.*
> \.java and even .* or just *. No results.
The issue is probably just with the syntax of your grep. All
:ProjectGrep does is temporarily set your working directory to the
root of your project and then delegates to vimgrep to do the rest of
the work. In your example you specified only *.java which to vimgrep
translates to: all files ending in '.java' in the current working
directory. What you probably meant to do was to search all java files
in all directories in the project, for which the syntax would be
**/*.java, like so:
:ProjectGrep /foo/ **/*.java
That should hopefully get you the search results you were expecting.
You can also take a look at vim's help for more information on
vimgrep and the file patterns that it will accept:
:help vimgrep
:help wildcards
> I'm using vim 7.1.314 and SpringSource 2.2.1 (which is basically
> Eclipse 3.5.1 under a different name) under Ubuntu Intrepid. (When I
> installed eclim, it complained about jdt not being up-to-date, but
> after trying a few things I figured it just didn't recognise it in
> SpringSource so I ignored it.)
One user has reported a possible issue[1] when using the Spring IDE,
however it their case it only affected source code validation. Let me
know if you experience this same issue.
[1]
http://sourceforge.net/tracker/?func=detail&atid=763323&aid=2507235&group_id=145869
--
eric