Mark occurrences is often completely wrong

[acarstoiu]

It may be that it's not tern that provides this functionality, but JSDT. No surprise here, but can you intercept the triggering events and make it properly? It is the local only (file) version of #339.

Thanks.

[angelozerr]

tern.java doesn't support mark occurrences and it will not. It's the goal of JSDT. JSDT 2.0 (Eclipse Neon) which is sonn available is a lot improve.

I close this issue.

[acarstoiu]

Well, I'm reporting this while running on Neon RC (JSDT 2.0.0).
Also, I wouldn't exclude taking care of occurrences in tern simply because this functionality is based on static code analysis, which is not at all the best ability of JSDT 👎

[angelozerr]

@acarstoiu I have seen some bugs about mark occurrences inside JSDT bugzilla. I suggeset you that you post your bug in the JSDT bugzilla.

JSDT Editor doesn't give the capability to override mark occurences, so it's not possible to do it with tern. I have no time to support that, but any contribution are welcome.

[acarstoiu]

If marking occurences is not override-able, then I guess the guys developing JSDT have reserved this issue for themselves. If only they used a proper parser...

[angelozerr]

JSDT 2.0.0 uses Esprima parser, but there is discussion to use Google closure.