>>> bread <breaddawson@...> seems to think that:
>I've used cedet for a while and found it's really easy and good for me to
>use. But there're several issues:
>1. It usually takes semantic several seconds (3~5 seconds) to load the
>completions when i use ' M-x semantic-ia-complete-symbol-menu'. But after
>the first load, it will be faster. But can it be faster on the first load? I
>used some other editors, such as ulipad for python programming, it responds
>very quickly to show the completions.
I think you want to change `semantic-idle-scheduler-work-idle-time'.
The work timer will pre-calculate the items you find slow.
>2. I found that semantic can not always find the completions. Sometimes i
>need to revert the buffer(maybe several times), then try 'M-x
>semantic-ia-complete-symbol-menu' again to find the completions. I don't
>know why, maybe semantic need to re-analyze the source code? If so, is that
>a way i can manually told semantic to analyze the source code right now?
In order to keep completion speedy, Semantic caches lots of info, and
builds dependency trees, so if you edit foo.h, files that include it
get their caches cleared. I've found a couple bugs similar to what
you describe, but I've fixed them. If next time it happens, you
discover reproduction steps, I'd like to know what they are.
>3. The last one is about nested including.
>For example, b.hpp includes a.hpp, c.hpp includes b.hpp. And finally i need
>to write a cpp file which includes c.hpp, just like this:
>c.cpp -> c.hpp -> b.hpp -> a.cpp
>where '->' indicates include.
>So if they are all in the same directory, or the directory has been added by
>'semantic-add-system-include', can i get all the class structures written in
>a.cpp via semantic?
Yes, it should.
>I tired several times, and found sometimes it can, sometime it can't. This
>is really confusing. Maybe it's something about EDE? But i have enable ede
[ ... ]
You need to use `semantic-analyze-debug-assist'. Whenever something
in completion doesn't work, you can use this to produce the analysis
information semantic is currently working with. Each time I find a
bug in a new corner, I usually update the output of this script. As
such, the output can be lengthy, as it includes the status of your
include files, unknown includes, local context analysis, and the
output of various stages of symbol lookup.
Eric Ludlam: eric@...
Siege: http://www.siege-engine.com Emacs: http://cedet.sourceforge.net