As I replicated your scenario as I understand it, and things worked
for me, I'm at a bit of a loss. Is this related to your earlier tramp
question. (ie, are these files accessed via tramp?)
Of course, if they are, I don't really know why that would make a
If you compare your setup commands in your .emacs, how might they be
different from those in the example install instructions? For example,
if you did:
M-x load-file RET ~/cedet/common/cedet.el RET -- or wherever it is
M-x semantic-load-enable-code-helpers RET
Now go to your sample with Human.h, and start with the command below
about idle work functions, and then try your repro steps again. This
should work even without an EDE project enabled.
On Wed, 2009-09-02 at 19:00 +0200, Michal wrote:
> hallo Eric & Group Memebers
> First of all sorry for doubled reply post. I just didn't get reply to
> may mailbox for 2 days so decided to resend it again.
> Unfortunately it still does not work for me.
> Please look at notes inside the reply.
> > From: Eric M. Ludlam <eric@......> - 2009-09-01 03:32
> > Hi,
> > I tried your example, and got the failed ability to jump between the
> > two parts. I guessed it was because not all the files had been parsed,
> > so I ran:
> > M-x semantic-debug-idle-work-function RET
> did it while in Human.h buffer (probably does not matter where I was then).
> > which I know just happens to parse all the files next to the file you
> > are in. Once this was done, I can now jump between the impl and
> > prototype and back again.
> > For more complex projects, you would need to get Semantic to parse your
> > key files ahead of time. The above function only helps for files in the
> > same directory as the current buffer. The semanticdb.sh script could be
> > used to initialize things ahead of time. It might help to use GNU
> > Global integration, though I haven't tried these two tools together in
> > this way. I'm guessing it would work.
> > This is a bit of a hairy problem, since one of the strengths in CEDET
> > for massive projects is that it will only parse the bits you use, which
> > is incompatible with the need for a global table of symbols. If CEDET
> > were to load in everything for a big project, it can overload your Emacs
> > session with big piles of useless tags you never access.
> > Hopefully these tricks can help get your working. The EDE trick you
> > have below is great for compilation and such, or for finding files by
> > name from includes.
> > The database output you have below indicates that you did successfully
> > parse all the files in your examples, so most of my advice above may be
> > moot. You can try:
> > M-z semantic-analyze-current-tag
> ] Name: "present"
> ] Class: #'semantic-analyze-references
> ] :tag present : void
> ] :tagdb : nil
> ] :scope #<semantic-scope-cache Cache>
> ] :rawsearchdata : nil
> > on the offending location to see what the reference analyzer output is.
> > I don't think there are any caches to flush, but if so, you can always
> > use the Senator menu item "Force Tag Refresh" to clear stuff.
> also done "Force Tag Refresh".
> > Eric
> best regards,
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> cedet-semantic mailing list