Community
Participate
Working Groups
"search scope for completion proposal" -> "search curren file and included files" absolutely without effect, not working at all. org.eclipse.cdt-3.0.0-I200506070932-linux.x86.tar.gz
Methinks Doug needs to clean up some UI for M7.
when is m7 sheduled? btw: which configuration-options exactly are responsible for auto-completion?
I have not implemented auto-completion in the new content assist. I never appreciated the completion popup in my face at seemingly random times. If content assist was faster, it might be worth it. But for now it is not.
I'll clean up the UI for RC1. This includes paying attention to the scope. I'll probably remove the configurability around auto-completion since I don't want to turn it on at this point.
> since I don't want to turn it on at this point. what exactly does that mean? i'm a big fan of autocompletion (maybe i am corrupted by java ;-) so disabling it will definitevely keep me off from using eclipse :-(
Yes, you are spoiled by the JDT. The CDT can take up to three seconds to present the proposals. Sometimes it's just faster to type it in yourself, in which case auto completion will just get in your way. If this is all that's keeping you off using Eclipse, then we've done a pretty good job ;-)
well ... it's not really all -- the last builds i tried was really slow and ate all of my cpu, but this (reported already) me be fixed rather soon ... but missing autocompletion, uhh ;-) btw: is it possible to reply to bugzilla's mails? i tried once and it didn't work but maybe i did something wrong.
(In reply to comment #4) > I'll clean up the UI for RC1. This includes paying attention to the scope. I'll > probably remove the configurability around auto-completion since I don't want to > turn it on at this point. I just ran across this bug myself after installing CDT M7. I can only ask that you do NOT remove this functionality. For people who have fast machines, it's not THAT much slower than the JDT. I think this is just a matter of preference, and if someone doesn't like using it, they can turn it off. How about just disabling the feature by default? I personally find it annoying to type CTRL+SPACE every time I want content assist. BTW, why is it slower than JDT? Does it not use the same technology? thanks, Barry
No, they don't use the same technology. Java parsers generally don't parse C++. Java doesn't have a preprocessor and, thus, inclusions. Parsing C++ is always slower than Java, no matter what tool you are looking at. I'll see what I can do about enabling auto-completion as an option. But for the life of me I can't see the value in auto completion. It's faster to type the Ctrl-Space than to wait the 500ms for auto completion to kick in, no?
But why does it have to use 500ms? You can set it to zero. Why is CTRL+SPACE faster than typing . -> or :: I don't get what you are saying at all. But thanks for looking into enabling it! -Barry
This is going to be risky to fix in RC1. I'll do it right after.
O.K. Completion now only uses search when "search current project" is selected. It actually skips by the time consuming parse in that scenario as well. But it does leave out anything local or unsaved/unindexed. I am just waiting on 102779 to actually search the current project instead of the whole workspace. Autoactivation has also been re-engaged.
All done. Search works quite nicely in content assist now.
Great! I will check it in RC2. BTW, is there a mailing list I can get on that just notifies when there is a new release available? thanks, Barry
Nope. I'll announce on the cdt-dev list and the cdt newsgroup.
