CEDET

When I try to use semantic-ia-fast-jump, the result is

"Could not find suitable jump point for *"

if the buffer containing the symbol is not open.  But it will jump to the
function if the buffer that contains the symbol is open.  I'm using
matlab-cedet.  Admittedly, I am a novice at cedet.  I saw some other posts
regarding the same issue, but no answers provided a solution.  I used the
latest code from trunk.

Thanks.

This is great news!

Thanks David!

Eric

On 12/05/2011 02:48 PM, David Engster wrote:
> Over the past weeks, I've been busy getting our new development branch
> ready, and I think it is now good enough for public testing. You can get
> it via
>
> bzr checkout bzr://cedet.bzr.sourceforge.net/bzrroot/cedet/code/newtrunk
>
> Compile it by calling 'make' and 'make install-info' (this will only
> install locally, unless you explicitly define INFODIR). If you want to
> use some special Emacs version, use 'make EMACS=emacsXYZ'.
>
> There are many, many things that have changed on that branch, but most
> of it is internal and shouldn't affect users. In a nutshell, this new
> trunk is the result of merging our 'file-rename' branch, which merged in
> the changes from Emacs, into our development branch 'trunk'. It is
> planned to make this 'newtrunk' our primary development branch in the
> near future. I've fixed dozens of conflicts, hundreds of byte compiler
> warnings and deprecated several old packages, and did so pretty
> rigorously, so I fully expect there to be glaring bugs. If you're
> currently in crunch time, it might not be such a good idea to
> switch... ;-)
>
> A few notes regarding the setup of that branch:
>
> - Emacs22 is not supported anymore. You need at least Emacs 23.1 to use
>    that branch. I tested compilation with Emacs 23.3 and Emacs24-bzr, and
>    it should compile without warnings there (only a few Wisent warnings,
>    which can be ignored).
>
> - Delete the cache files in ~/.semanticdb (also do that if you switch
>    back to 'trunk').
>
> - Load CEDET by putting
>
>    (load-file "<PATH TO NEWTRUNK>/cedet-devel-load.el")
>
>   into your .emacs. This should happen very much at the beginning, so
>   that it can do its work before parts of CEDET from Emacs proper are
>   loaded.
>
> - You can still activate CEDET by calling one of the 'canned
>    configurations', like
>
>    (semantic-load-enable-code-helpers)
>
>    However, note that Semantic was changed to work as a 'mode' now,
>    called 'semantic-mode'. So the 'new way' to activate it would be by
>    doing
>
>      ;; Add minor-modes which should be loaded
>      (add-to-list 'semantic-default-submodes 'global-semantic-idle-summary-mode)
>      (add-to-list 'semantic-default-submodes 'global-semantic-mru-bookmark-mode)
>      ;; Activate semantic
>      (semantic-mode 1)
>
>    See the doc-string of `semantic-default-submodes' to see what else you
>    can add.
>
> - EDE is still activated using
>
>    (global-ede-mode 1)
>
> - Senator still exists, but its menu was integrated into a new general
>    menu item called 'Development'.
>
> - Note that this should really be *all* to get CEDET running
>    initially. If you're tweaking some variables, it could be that you
>    first have to 'require' some CEDET feature to make them work. You'll
>    have to adapt those requires to the new naming scheme (which was
>    introduced to avoid name clashes on 8+3 systems - don't ask). For
>    example,
>
>    (require 'semantic-c)
>    (require 'ede-proj)
>
>    has to be changed into
>
>    (require 'semantic/bovine/c)
>    (require 'ede/proj)
>
>    I know that's a bummer, and we probably could set something up to make
>    the old requires working, but that would be ugly and error prone, so
>    I'd rather do a clean cut now. Rule of thumb is:
>
>      * Change '-' to '/'
>
>      * Language implementations are in semantic/bovine or
>        semantic/wisent.
>
> Please try to do your normal stuff using 'newtrunk' and let me know how
> it works out. You can of course also report 'normal' bugs, as always,
> but regressions have priority at the moment.
>
> Cheers,
> David
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Cedet-devel mailing list
> Cedet-devel@...
> https://lists.sourceforge.net/lists/listinfo/cedet-devel
>

There seems to be a bug in srecode-el.srt:

  ----
 (defcustom $?NAME$ $^$
   "*$DOC$"
   :group $GROUP$
   :type $?CUSTOMTYPE$)

There seems to be a quote missing in front of $GROUP$
The same bug is present in srecode/el.srt in the cedet-new branch.

 HTH Ralf Mattes

In normal TAGS i can M-* to jump to the place where i last searched for 
a tag. The cool part is that the "places where i last searched for a 
tag" form a lifo that is extremely handy. There must be some 
functionality in cedet to match that, but i have faild to spot it. Any help?
Thnx!

On Sat, Dec 3, 2011 at 4:13 AM, Eric M. Ludlam <ericludlam@...> wrote:
>
> I'm glad you solved your puzzle.  There are two java parsers.  One is
> for creating just java tags.  The other broader parser is a full parser
> for Java that handles some of the other syntax better.  The full parser
> can be a little slower, and is a little less robust to code errors, so
> the tagging parser is the default.
>
> You can use the new parser by easily enough. I think the switch is as
> easy as removing the autoload tag from wisent-java-default-setup in
> wisent-java-tags.el, and adding it into wisent-java.el for the same
> function, and doing a full rebuild to change which file is used.
>
> If that doesn't solve the above, then that would be the best place to
> put your Java 7 upgrades. :)
>

I'll look into this.

Is there a good way to manually run the parser on a file and see the
result/the parse erros? IE how do you debug parser?

cheers
/Joel

> On 11/27/2011 12:40 AM, Alastair Rankine wrote:
>> 
>> As part of the current work I need to get my project class to get notified whenever the configuration-default slot is changed. Unfortunately there doesn't seem a way of doing this using the standard EIEIO framework (unless I am missing something), so instead I'm proposing the following patch to ede-project-configurations-set.

> 

> A reasonable idea, though I wonder why you need notification? Everything I'm familiar with polls the value as needed, such as menus and compilation.

Actually you are quite correct, a fact I realised after sending that patch through. I subsequently updated my branch to lazily calculate the build directory depending on the current setting of the configuration-default slot.