| "Debug" interface for the indexer [message #148283] |
Wed, 06 July 2005 11:32  |
Eclipse User |
|
|
|
I have read a number of threads about problems using the indexer, and
I've certainly had my share. On the other hand, some of the responses
from the developers sound like it's capable of doing some really great
stuff. My guess is that there are perhaps some subtle or just
difficult-to-see configuration problems that are getting in the way. If
we could diagnose what we're doing "wrong", then I bet we could all have
more indexer goodness than we can handle.
Unfortunately, when something goes wrong, the only symptoms are things
like "I can't use ctrl-leftbutton to navigate" or some error message in
the status bar that doesn't really point out the problem.
I'm thinking that a lot of problems could potentially be short circuited
if the state of the indexer was more visible. I can't say I have any
idea what this interface would look like, but my fantasy is to be able
to spend a few minutes concentrating on some helpful data and then say
"Oh - I see that I forgot to tell it about this include directory" or
"Oh - it doesn't seem to be picking up this include file anywhere, I
wonder if it's missing" or something else that begins with "Oh".
In summary, if there's any way to create more visibility into the state
of the indexer, I think more people could solve their problems by
themselves and it would be easier to help those who couldn't.
|
|
|
| Re: "Debug" interface for the indexer [message #148287 is a reply to message #148283] |
Wed, 06 July 2005 11:51  |
| Eclipse User |
|
|
|
Originally posted by: matthias.digitalraidREMOVETHIS.com
Patrick Turley wrote:
> I'm thinking that a lot of problems could potentially be short circuited
> if the state of the indexer was more visible.
<snip>
> In summary, if there's any way to create more visibility into the state
> of the indexer, I think more people could solve their problems by
> themselves and it would be easier to help those who couldn't.
Good point. If for example error messages would be more verbose (or
existent at all!), we could also file more precise bug reports. I also
had trouble just recently describing a bug with the broken content
assist, because everything I noticed was:
1. It doesn't work
2. Statusbar shows that a NullPointerException occured
That doesn't help a lot to track down the error.
Regards,
Matthias
|
|
|
Powered by
FUDForum. Page generated in 0.02918 seconds
Home