>>> David <de_bb@...> seems to think that:
>I'm using the latest CEDET from CVS with Emacs 22.2.
>Sometimes I get the following error:
>Idle Parse Error: "#<buffer XYZ> - Wrong type argument: (or object-p class-p), nil" [3 times]
>or this one:
>eieio-oref: Wrong type argument: (or object-p class-p), nil
>I'd love to give a full backtrace, but somehow debug-on-error doesn't do
>the trick here.
I've been trying to find and track these down too. You can use:
will produce a nice stack. Thanks.
>Another problem is with smart completion in ELisp buffers. If I load an
>ELisp file, it gets correctly scanned and I can see all the variables,
>defuns, etc. in the TAGS menu. I can also navigate with the senator
>jumping commands, but the smart completion doesn't work until I do an
>M-x eval-buffer - then, suddenly, everything works as expected. Is this
>the wanted behaviour? Do I first have to eval the buffer to get smart
>completion to work?
[ ... ]
The Emacs Lisp support has both the parsing part, and an "omniscient"
database that queries Emacs' known symbols. It seems likely that the
include path technique isn't working quite right, but when you eval
the buffer, the omniscient database starts working, and lets symbols
I haven't worked much on Semantic's smart completion for Emacs Lisp
because the existing tools are very good, so I use those.
Eric Ludlam: eric@...
Siege: http://www.siege-engine.com Emacs: http://cedet.sourceforge.net