CEDET

Hi,


  The warnings are all because I want to make sure that programs that
depend on semantic are advised how to update from the 1.4 API to the
semantic 2 API.  Since I still have a semantic 1.4 API in semantic, it
throws a lot of warnings.  Those will eventually go away when the 1.4
stuff is completely eliminated.

  As for your error, it seems as though cc-mode isn't loading at all.
Getting that fixed seems like the first order of business.  If you're
local Emacs install has used a substitute C mode of some sort that you
need/want to use, then you would need to port the Semantic support of
C parsing to the new mode.  It might be as simple as converting the
line:

(require 'cc-mode)

with

(require 'my-c-mode-substitue)

but there might be syntax table differences that would cause erroneous
behaviors.

Good Luck
Eric

>>> Christopher White <chris@...> seems to think that:
>Hello all,
>
>Trying to make some headway with using CEDET, as it looks very powerful.
>However, I'm running into a couple of issues while compiling.
>
>I synced up latest in CVS and I'm running Emacs version 21.4.1 on Linux.
>(BTW, also saw the same problem with 1.0pre3).
>
>The problem occurs while byte-compiling semantic-c.el:
>
>The line for "(require 'cc-mode)" causes problems.  I can't quite figure
>out why.  I've isolated the byte-compile command that causes it:
>
>[safire] cedet/semantic/bovine --# "emacs" -batch --no-site-file -l
>languages-compile-script -f batch-byte-compile  semantic-c.el
>Loading /usr/libexec/emacs/21.4/i686-redhat-linux-gnu/fns-21.4.1-x.el
>(source)...
>While compiling toplevel forms in
>file /usr/src/cedet/semantic/bovine/semantic-c.el:
>  ** variable `semantic-format-tag-functions' obsoletes, but isn't alias
>of `semantic-token->text-functions'
>  ** variable `semantic-tag-expand-function' obsoletes, but isn't alias
>of `semantic-expand-nonterminal'
>  ** variable `semantic--parse-table' obsoletes, but isn't alias of
>`semantic-toplevel-bovine-table'
>  ** variable `semantic--buffer-cache' obsoletes, but isn't alias of
>`semantic-toplevel-bovine-cache'
>  ** variable `semantic--before-fetch-tags-hook' obsoletes, but isn't
>alias of `semantic-before-toplevel-bovination-hook'
>  ** variable `semantic-working-type' obsoletes, but isn't alias of
>`semantic-bovination-working-type'
>  ** variable `semantic-format-tag-functions' obsoletes, but isn't alias
>of `semantic-token->text-functions'
>  ** variable `semantic-format-tag-custom-list' obsoletes, but isn't
>alias of `semantic-token->text-custom-list'
>  ** variable `semantic-format-face-alist' obsoletes, but isn't alias of
>`semantic-face-alist'
>  ** variable `semantic-imenu-expand-type-members' obsoletes, but isn't
>alias of `semantic-imenu-expand-type-parts'
>  ** variable `semantic-imenu-bucketize-type-members' obsoletes, but
>isn't alias of `semantic-imenu-bucketize-type-parts'
>  ** variable `semantic-imenu-expandable-tag-classes' obsoletes, but
>isn't alias of `semantic-imenu-expandable-token'
>  ** variable `semantic-step-at-tag-classes' obsoletes, but isn't alias
>of `semantic-step-at-token-ids'
>  ** variable `senator-step-at-start-end-tag-classes' obsoletes, but
>isn't alias of `senator-step-at-start-end-token-ids'
>  ** variable `senator-add-log-tags' obsoletes, but isn't alias of
>`senator-add-log-tokens'
>  !! File error (("Cannot open load file" "cc-defs.el"))
>Done
>
>If I comment out the require line, it compiles ok, but then later I get
>an error when I actually start emacs - the autoload of function
>"semantic-default-c-setup" fails.  I suspect it's related to the compile
>problem, but not positive.
>
>Also, there are a large number of such warnings...I assume this are all
>ok?
>
>Thanks
>...cj
  [ ... ]

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

Thanks Eric,

After a fair amount of playing around and debugging the problem, it
appears that it has do with with cc-mode and a strange dependency on
"cc-defs.el" when all I have is "cc-defs.elc".  After installing emacs
lisp sources the problem went away!  Now things compile cleanly.

Now that it's up and running, I'll play with it for a while.

One quick question - I notice that it makes a big difference if my
include uses <> or "" as in:

#include <path/include.hh>

In the project I'm working on, project header files are frequently
specified using the <> syntax.  As such, it seems that semantic doesn't
find it.  If I change to "" it will find classes.

Also, is there a way to have a full project parsed, similar to ctags?
For example, all *.cc and *.hh files in /dir/to/project should be
searched.  I started with "semanticdb-create-system-database" but I
don't really see any effect on completion.

Thanks for your help.  I'm very impressed with the output generated by
this.

...cj

On Sun, 2007-05-20 at 10:29 -0400, Eric M. Ludlam wrote:
> Hi,
> 
> 
>   The warnings are all because I want to make sure that programs that
> depend on semantic are advised how to update from the 1.4 API to the
> semantic 2 API.  Since I still have a semantic 1.4 API in semantic, it
> throws a lot of warnings.  Those will eventually go away when the 1.4
> stuff is completely eliminated.
> 
>   As for your error, it seems as though cc-mode isn't loading at all.
> Getting that fixed seems like the first order of business.  If you're
> local Emacs install has used a substitute C mode of some sort that you
> need/want to use, then you would need to port the Semantic support of
> C parsing to the new mode.  It might be as simple as converting the
> line:
> 
> (require 'cc-mode)
> 
> with
> 
> (require 'my-c-mode-substitue)
> 
> but there might be syntax table differences that would cause erroneous
> behaviors.
> 
> Good Luck
> Eric
> 
> >>> Christopher White <chris@...> seems to think that:
> >Hello all,
> >
> >Trying to make some headway with using CEDET, as it looks very powerful.
> >However, I'm running into a couple of issues while compiling.
> >
> >I synced up latest in CVS and I'm running Emacs version 21.4.1 on Linux.
> >(BTW, also saw the same problem with 1.0pre3).
> >
> >The problem occurs while byte-compiling semantic-c.el:
> >
> >The line for "(require 'cc-mode)" causes problems.  I can't quite figure
> >out why.  I've isolated the byte-compile command that causes it:
> >
> >[safire] cedet/semantic/bovine --# "emacs" -batch --no-site-file -l
> >languages-compile-script -f batch-byte-compile  semantic-c.el
> >Loading /usr/libexec/emacs/21.4/i686-redhat-linux-gnu/fns-21.4.1-x.el
> >(source)...
> >While compiling toplevel forms in
> >file /usr/src/cedet/semantic/bovine/semantic-c.el:
> >  ** variable `semantic-format-tag-functions' obsoletes, but isn't alias
> >of `semantic-token->text-functions'
> >  ** variable `semantic-tag-expand-function' obsoletes, but isn't alias
> >of `semantic-expand-nonterminal'
> >  ** variable `semantic--parse-table' obsoletes, but isn't alias of
> >`semantic-toplevel-bovine-table'
> >  ** variable `semantic--buffer-cache' obsoletes, but isn't alias of
> >`semantic-toplevel-bovine-cache'
> >  ** variable `semantic--before-fetch-tags-hook' obsoletes, but isn't
> >alias of `semantic-before-toplevel-bovination-hook'
> >  ** variable `semantic-working-type' obsoletes, but isn't alias of
> >`semantic-bovination-working-type'
> >  ** variable `semantic-format-tag-functions' obsoletes, but isn't alias
> >of `semantic-token->text-functions'
> >  ** variable `semantic-format-tag-custom-list' obsoletes, but isn't
> >alias of `semantic-token->text-custom-list'
> >  ** variable `semantic-format-face-alist' obsoletes, but isn't alias of
> >`semantic-face-alist'
> >  ** variable `semantic-imenu-expand-type-members' obsoletes, but isn't
> >alias of `semantic-imenu-expand-type-parts'
> >  ** variable `semantic-imenu-bucketize-type-members' obsoletes, but
> >isn't alias of `semantic-imenu-bucketize-type-parts'
> >  ** variable `semantic-imenu-expandable-tag-classes' obsoletes, but
> >isn't alias of `semantic-imenu-expandable-token'
> >  ** variable `semantic-step-at-tag-classes' obsoletes, but isn't alias
> >of `semantic-step-at-token-ids'
> >  ** variable `senator-step-at-start-end-tag-classes' obsoletes, but
> >isn't alias of `senator-step-at-start-end-token-ids'
> >  ** variable `senator-add-log-tags' obsoletes, but isn't alias of
> >`senator-add-log-tokens'
> >  !! File error (("Cannot open load file" "cc-defs.el"))
> >Done
> >
> >If I comment out the require line, it compiles ok, but then later I get
> >an error when I actually start emacs - the autoload of function
> >"semantic-default-c-setup" fails.  I suspect it's related to the compile
> >problem, but not positive.
> >
> >Also, there are a large number of such warnings...I assume this are all
> >ok?
> >
> >Thanks
> >...cj
>   [ ... ]
>

Hi,

  I recently posted about how to get CEDET/CVS working with the linux
kernel, which has similar problems.

  If you read the info file in cedet/semantic/doc/semantic.info, and
navigate to the chapter "Installation/Basic Configuration" and look at
the Search Optimization section.

  If that doesn't help, please let me know what could be improved, and
then go to my post on the mailing list from a couple days ago.  The
archives are currently unavailable, so I can't forward you the URL.

  The core difference you identified is that <> is supposed to be for
system includes, and "" for project includes.  Therefore, you need to
add the project path to include files to your system include path.

  Once you do that, you don't need to pre-parse anything, though using
`semanticdb-create-ebrowse-database' can likely make things go faster.

Good Luck
Eric

>>> Christopher White <chris@...> seems to think that:
>Thanks Eric,
>
>After a fair amount of playing around and debugging the problem, it
>appears that it has do with with cc-mode and a strange dependency on
>"cc-defs.el" when all I have is "cc-defs.elc".  After installing emacs
>lisp sources the problem went away!  Now things compile cleanly.
>
>Now that it's up and running, I'll play with it for a while.
>
>One quick question - I notice that it makes a big difference if my
>include uses <> or "" as in:
>
>#include <path/include.hh>
>
>In the project I'm working on, project header files are frequently
>specified using the <> syntax.  As such, it seems that semantic doesn't
>find it.  If I change to "" it will find classes.
>
>Also, is there a way to have a full project parsed, similar to ctags?
>For example, all *.cc and *.hh files in /dir/to/project should be
>searched.  I started with "semanticdb-create-system-database" but I
>don't really see any effect on completion.
>
>Thanks for your help.  I'm very impressed with the output generated by
>this.
>
>...cj
>
>On Sun, 2007-05-20 at 10:29 -0400, Eric M. Ludlam wrote:
>> Hi,
>> 
>> 
>>   The warnings are all because I want to make sure that programs that
>> depend on semantic are advised how to update from the 1.4 API to the
>> semantic 2 API.  Since I still have a semantic 1.4 API in semantic, it
>> throws a lot of warnings.  Those will eventually go away when the 1.4
>> stuff is completely eliminated.
>> 
>>   As for your error, it seems as though cc-mode isn't loading at all.
>> Getting that fixed seems like the first order of business.  If you're
>> local Emacs install has used a substitute C mode of some sort that you
>> need/want to use, then you would need to port the Semantic support of
>> C parsing to the new mode.  It might be as simple as converting the
>> line:
>> 
>> (require 'cc-mode)
>> 
>> with
>> 
>> (require 'my-c-mode-substitue)
>> 
>> but there might be syntax table differences that would cause erroneous
>> behaviors.
>> 
>> Good Luck
>> Eric
>> 
>> >>> Christopher White <chris@...> seems to think that:
>> >Hello all,
>> >
>> >Trying to make some headway with using CEDET, as it looks very powerful.
>> >However, I'm running into a couple of issues while compiling.
>> >
>> >I synced up latest in CVS and I'm running Emacs version 21.4.1 on Linux.
>> >(BTW, also saw the same problem with 1.0pre3).
>> >
>> >The problem occurs while byte-compiling semantic-c.el:
>> >
>> >The line for "(require 'cc-mode)" causes problems.  I can't quite figure
>> >out why.  I've isolated the byte-compile command that causes it:
>> >
>> >[safire] cedet/semantic/bovine --# "emacs" -batch --no-site-file -l
>> >languages-compile-script -f batch-byte-compile  semantic-c.el
>> >Loading /usr/libexec/emacs/21.4/i686-redhat-linux-gnu/fns-21.4.1-x.el
>> >(source)...
>> >While compiling toplevel forms in
>> >file /usr/src/cedet/semantic/bovine/semantic-c.el:
>> >  ** variable `semantic-format-tag-functions' obsoletes, but isn't alias
>> >of `semantic-token->text-functions'
>> >  ** variable `semantic-tag-expand-function' obsoletes, but isn't alias
>> >of `semantic-expand-nonterminal'
>> >  ** variable `semantic--parse-table' obsoletes, but isn't alias of
>> >`semantic-toplevel-bovine-table'
>> >  ** variable `semantic--buffer-cache' obsoletes, but isn't alias of
>> >`semantic-toplevel-bovine-cache'
>> >  ** variable `semantic--before-fetch-tags-hook' obsoletes, but isn't
>> >alias of `semantic-before-toplevel-bovination-hook'
>> >  ** variable `semantic-working-type' obsoletes, but isn't alias of
>> >`semantic-bovination-working-type'
>> >  ** variable `semantic-format-tag-functions' obsoletes, but isn't alias
>> >of `semantic-token->text-functions'
>> >  ** variable `semantic-format-tag-custom-list' obsoletes, but isn't
>> >alias of `semantic-token->text-custom-list'
>> >  ** variable `semantic-format-face-alist' obsoletes, but isn't alias of
>> >`semantic-face-alist'
>> >  ** variable `semantic-imenu-expand-type-members' obsoletes, but isn't
>> >alias of `semantic-imenu-expand-type-parts'
>> >  ** variable `semantic-imenu-bucketize-type-members' obsoletes, but
>> >isn't alias of `semantic-imenu-bucketize-type-parts'
>> >  ** variable `semantic-imenu-expandable-tag-classes' obsoletes, but
>> >isn't alias of `semantic-imenu-expandable-token'
>> >  ** variable `semantic-step-at-tag-classes' obsoletes, but isn't alias
>> >of `semantic-step-at-token-ids'
>> >  ** variable `senator-step-at-start-end-tag-classes' obsoletes, but
>> >isn't alias of `senator-step-at-start-end-token-ids'
>> >  ** variable `senator-add-log-tags' obsoletes, but isn't alias of
>> >`senator-add-log-tokens'
>> >  !! File error (("Cannot open load file" "cc-defs.el"))
>> >Done
>> >
>> >If I comment out the require line, it compiles ok, but then later I get
>> >an error when I actually start emacs - the autoload of function
>> >"semantic-default-c-setup" fails.  I suspect it's related to the compile
>> >problem, but not positive.
>> >
>> >Also, there are a large number of such warnings...I assume this are all
>> >ok?
>> >
>> >Thanks
>> >...cj
>>   [ ... ]
>> 
>
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by DB2 Express
>Download DB2 Express C - the FREE version of DB2 express and take
>control of your XML. No limits. Just data. Click to get it now.
>http://sourceforge.net/powerbar/db2/
>_______________________________________________
>cedet-semantic mailing list
>cedet-semantic@...
>https://lists.sourceforge.net/lists/listinfo/cedet-semantic
>

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

>>> Hadron <hadronquark@...> seems to think that:
>
>
>(1) Persistence of semantic completion.
>
>If I add this line to some C
>
>struct fstab fs;
>
>and then try to complete "fs.", it doesn't work. This is fine. So I add
>
>#include <fstab.h>
>
>Still doesnt complete "fs.". OK, so I visit the file. Bingo! Completion
>now works. So far as I expected.
>
>I then do a semanticdb-save-all-db. So why doesnt it remember the
>fstab.h completion candidates the next time I open my test file and try
>to complete "fs."? What does the save function actually save?

The save function saves tags by directory based on
`semanticdb-persistent-path'.  Please see the doc to see how to
customize it.  Since you want to save stuff related to /usr/include
type files, you should also investigate the variable
`semanticdb-default-save-directory'.

The original lookup of fstab.h was skipped as an optimization of the
semanticdb search routines due to `semanticdb-find-default-throttle'
which has been a source of confusion and bugs recently.  The CVS
version should be better and more reliable than what is in 1.0pre3.


>(2) semantic search
>
>There is a blur in my mind between tags and semantic search. Can someone
>explain how & what the differences are.
>
>If I have a few files open, cant I use a semantic search to locate a
>varable definition? At the moment I use cscope for that. So whats the
>use of the semantic search functions? They appear to be no more than in
>"in buffer" search. Does semantic offer a "jump to definition"
>functionality similar to cscope?
>
>thanks for any explanations and/or pointers.

semantic-search is used by semanticdb-search, which is used by all the
completion routines to find the symbols for doing smart completion.
You can do raw jumping about with the keybinding (from senator)
"C-c . J".

Good Luck
Eric

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

Hi, Hadron, Eric, and others

I went through some of the same difficulty with semantic intellisense
completion a couple of months ago.  i hope that you guys don't mind me
putting my two cents in.  please correct me on any of these points if
i'm wrong

first, semantic does require that you include the header file of
interest in order to get completion on any symbols.  to me this seems
to be a nice optimization.  by default semantic performs a recursive
search through included header files to collect tags for completion,
so if your fstab.h header file includes other header files that are
needed to perform the completion they will be searched.

second, and way more important, usually semantic needs to be able to
find the header file itself in the filesystem before it gets it's
tags.  it needs the full path to the header before it tries to find
the tag table for the header in any database.  semantic stores tag
caches on a directory by directory basis, so it wants the full path to
the file to know which directory cache to look in.

for system databases, i found that i needed to add the path in
manually before creating the database.  i put this in my .emacs.

(defun semantic-c-mode-hook ()
 (semantic-add-system-include "/path/to/header/files"))
(add-hook 'c-mode-common-hook 'semantic-c-mode-hook)
(add-hook 'c-mode-hook 'semantic-c-mode-hook)

one easy way to make sure that semantic is indeed caching tags and
creating system databases correctly is by looking for a file called
"semantic.cache"  in the directory of interest.  it is a text file and
you can look through it.  by the way, if you try to create a database
where you don't have permission to write a file i think it will fail
... i always put this in my .emacs.

(setq semanticdb-default-save-directory "/home/directory/.semanticdb")

and it stores all of the caches there.

finally, if the "unloaded" flag is not set in the
semanticdb-find-default-throttle, semantic will not automatically open
a header file that it has never seen, even if it has the path to it.

Jamie


On 5/6/07, Hadron <hadronquark@...> wrote:
>
>
> (1) Persistence of semantic completion.
>
> If I add this line to some C
>
> struct fstab fs;
>
> and then try to complete "fs.", it doesn't work. This is fine. So I add
>
> #include <fstab.h>
>
> Still doesnt complete "fs.". OK, so I visit the file. Bingo! Completion
> now works. So far as I expected.
>
> I then do a semanticdb-save-all-db. So why doesnt it remember the
> fstab.h completion candidates the next time I open my test file and try
> to complete "fs."? What does the save function actually save?
>
> (2) semantic search
>
> There is a blur in my mind between tags and semantic search. Can someone
> explain how & what the differences are.
>
> If I have a few files open, cant I use a semantic search to locate a
> varable definition? At the moment I use cscope for that. So whats the
> use of the semantic search functions? They appear to be no more than in
> "in buffer" search. Does semantic offer a "jump to definition"
> functionality similar to cscope?
>
> thanks for any explanations and/or pointers.
>
>
> --
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> cedet-semantic mailing list
> cedet-semantic@...
> https://lists.sourceforge.net/lists/listinfo/cedet-semantic
>

Hi, Hadron, Eric, and others

I went through some of the same difficulty with semantic intellisense
completion a couple of months ago.  i hope that you guys don't mind me
putting my two cents in.  please correct me on any of these points if
i'm wrong

first, semantic does require that you include the header file of
interest in order to get completion on any symbols.  to me this seems
to be a nice optimization.  by default semantic performs a recursive
search through included header files to collect tags for completion,
so if your fstab.h header file includes other header files that are
needed to perform the completion they will be searched.

second, and way more important, usually semantic needs to be able to
find the header file itself in the filesystem before it gets it's
tags.  it needs the full path to the header before it tries to find
the tag table for the header in any database.  semantic stores tag
caches on a directory by directory basis, so it wants the full path to
the file to know which directory cache to look in.

for system databases, i found that i needed to add the path in
manually before creating the database.  i put this in my .emacs.

(defun semantic-c-mode-hook ()
 (semantic-add-system-include "/path/to/header/files"))
(add-hook 'c-mode-common-hook 'semantic-c-mode-hook)
(add-hook 'c-mode-hook 'semantic-c-mode-hook)

one easy way to make sure that semantic is indeed caching tags and
creating system databases correctly is by looking for a file called
"semantic.cache"  in the directory of interest.  it is a text file and
you can look through it.  by the way, if you try to create a database
where you don't have permission to write a file i think it will fail
... i always put this in my .emacs.

(setq semanticdb-default-save-directory "/home/directory/.semanticdb")

and it stores all of the caches there.

finally, if the "unloaded" flag is not set in the
semanticdb-find-default-throttle, semantic will not automatically open
a header file that it has never seen, even if it has the path to it.

Jamie


On 5/6/07, Hadron <hadronquark@...> wrote:
>
>
> (1) Persistence of semantic completion.
>
> If I add this line to some C
>
> struct fstab fs;
>
> and then try to complete "fs.", it doesn't work. This is fine. So I add
>
> #include <fstab.h>
>
> Still doesnt complete "fs.". OK, so I visit the file. Bingo! Completion
> now works. So far as I expected.
>
> I then do a semanticdb-save-all-db. So why doesnt it remember the
> fstab.h completion candidates the next time I open my test file and try
> to complete "fs."? What does the save function actually save?
>
> (2) semantic search
>
> There is a blur in my mind between tags and semantic search. Can someone
> explain how & what the differences are.
>
> If I have a few files open, cant I use a semantic search to locate a
> varable definition? At the moment I use cscope for that. So whats the
> use of the semantic search functions? They appear to be no more than in
> "in buffer" search. Does semantic offer a "jump to definition"
> functionality similar to cscope?
>
> thanks for any explanations and/or pointers.
>
>
> --
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> cedet-semantic mailing list
> cedet-semantic@...
> https://lists.sourceforge.net/lists/listinfo/cedet-semantic
>

"Jamie Macbeth" <jamie.macbeth@...> writes:

> Hi, Hadron, Eric, and others
>
> I went through some of the same difficulty with semantic intellisense
> completion a couple of months ago.  i hope that you guys don't mind me
> putting my two cents in.  please correct me on any of these points if
> i'm wrong
>
> first, semantic does require that you include the header file of
> interest in order to get completion on any symbols.  to me this seems

The file must be re-opened too which is a pain to be honest. Eric has
indicated he might change this in the future. I would sooner wait for 10
seconds when I open a C program than have to manually track and open
each header file which includes values I wish to complete on.

> to be a nice optimization.  by default semantic performs a recursive
> search through included header files to collect tags for completion,
> so if your fstab.h header file includes other header files that are
> needed to perform the completion they will be searched.

A recent correspondence suggests that some of the clever c wizardry in
the Linux headers might just not be handled properly at the moment by
semantic parser :( (What *do* the Linux app programmers use for
completion etc ?). Surely not that java horror Eclipse :-; ?

>
> second, and way more important, usually semantic needs to be able to
> find the header file itself in the filesystem before it gets it's
> tags.  it needs the full path to the header before it tries to find
> the tag table for the header in any database.  semantic stores tag
> caches on a directory by directory basis, so it wants the full path to
> the file to know which directory cache to look in.
>
> for system databases, i found that i needed to add the path in
> manually before creating the database.  i put this in my .emacs.
>
> (defun semantic-c-mode-hook ()
> (semantic-add-system-include "/path/to/header/files"))
> (add-hook 'c-mode-common-hook 'semantic-c-mode-hook)
> (add-hook 'c-mode-hook 'semantic-c-mode-hook)

I pointed this to the root of my (local) Linux header hierarchy and
still no joy.

>
> one easy way to make sure that semantic is indeed caching tags and
> creating system databases correctly is by looking for a file called
> "semantic.cache"  in the directory of interest.  it is a text file and
> you can look through it.  by the way, if you try to create a database
> where you don't have permission to write a file i think it will fail
> ... i always put this in my .emacs.
>
> (setq semanticdb-default-save-directory "/home/directory/.semanticdb")

Yup - I had that since at one stage I didnt keep a local copy.

>
> and it stores all of the caches there.
>
> finally, if the "unloaded" flag is not set in the
> semanticdb-find-default-throttle, semantic will not automatically open
> a header file that it has never seen, even if it has the path to it.

I believe from earlier comments from Eric that this is broken.

I have a situation at the moment where even if I open the file of
interest (in my local Linux header hierarchy) it is not parsing and
creating a cache file which makes me wonder if I have to add each and
every directory to the system-include?

The paths confuse me. I see no real reason to differentiate between
"system headers" and "project headers". Simply have a set of paths each
of which is the root of a hierarchy to search - and an option to follow
symbolic links. I would say that how semantic locates files is the most
difficult for a noob at the moment. I am pretty sure I read something
somewhere in the docs that it ignores certain system files too - but I
cant find it again.

>
> Jamie

Just while on the subject and Jamie is involved, here is my biggest
issue at the moment with regard to paths and selective parsing. In the
following "joke/testbed code" notice 

1) inclusion of fstab.h. This is in /usr/include.
2) the inclusion of <asm/thread_info.h>. This is in
~/programming/c/linux.....

All files have been "cscope'd" for easy file opening from structure references.

I open my test file and move to the line "pfstabEntry->". I try inline
completion. I do not get the structure values. I open the
/usr/include/fstab.h using cscope navigation command, and *then*
completion works. Semantic is now aware of fstab.

However, if I move to the "pti->" line having opened the thread_info.h
file in a similar way, then completion does not work. I know this is
going to be down to some path issue, but I tried Jamie's suggestion
earlier specifying the complete directory as well as header root for the
thread_info file in the c-mode-hook e.g

,----
| (defun semantic-c-mode-hook ()
| (semantic-add-system-include "/home/programming/c/linux-source-2.6.20/include/asm"))
| (add-hook 'c-mode-common-hook 'semantic-c-mode-hook)
| (add-hook 'c-mode-hook 'semantic-c-mode-hook)
`----


C test Code below.


#include <stdio.h>
#include <stdlib.h>
#include <fstab.h>
#include <gtk/gtk.h>
#include <sched.h>
#include <asm/thread_info.h>

#include "filesystems.h"

/* START GLOBALS */
/* The head of the fstab copies */
GList * pfstab;
struct fstab * pfstabEntry = p;
struct thread_info * pti;
/* END GLOBALS */


/* release all memory reserved for a temporary fstab structure */
void fstabFreeEntry(gpointer p, gpointer ignore){
	pti->
	pfstabEntry->
	g_free(pfstabEntry->fs_spec);
	g_free(pfstabEntry->fs_file);
	g_free(pfstabEntry->fs_vfstype);
	g_free(pfstabEntry->fs_);
	g_free(p);
}




"Jamie Macbeth" <jamie.macbeth@...> writes:

> Hi, Hadron, Eric, and others
>
> I went through some of the same difficulty with semantic intellisense
> completion a couple of months ago.  i hope that you guys don't mind me
> putting my two cents in.  please correct me on any of these points if
> i'm wrong
>
> first, semantic does require that you include the header file of
> interest in order to get completion on any symbols.  to me this seems
> to be a nice optimization.  by default semantic performs a recursive
> search through included header files to collect tags for completion,
> so if your fstab.h header file includes other header files that are
> needed to perform the completion they will be searched.
>
> second, and way more important, usually semantic needs to be able to
> find the header file itself in the filesystem before it gets it's
> tags.  it needs the full path to the header before it tries to find
> the tag table for the header in any database.  semantic stores tag
> caches on a directory by directory basis, so it wants the full path to
> the file to know which directory cache to look in.
>
> for system databases, i found that i needed to add the path in
> manually before creating the database.  i put this in my .emacs.
>
> (defun semantic-c-mode-hook ()
> (semantic-add-system-include "/path/to/header/files"))
> (add-hook 'c-mode-common-hook 'semantic-c-mode-hook)
> (add-hook 'c-mode-hook 'semantic-c-mode-hook)
>
> one easy way to make sure that semantic is indeed caching tags and
> creating system databases correctly is by looking for a file called
> "semantic.cache"  in the directory of interest.  it is a text file and
> you can look through it.  by the way, if you try to create a database
> where you don't have permission to write a file i think it will fail
> ... i always put this in my .emacs.
>
> (setq semanticdb-default-save-directory "/home/directory/.semanticdb")
>
> and it stores all of the caches there.
>
> finally, if the "unloaded" flag is not set in the
> semanticdb-find-default-throttle, semantic will not automatically open
> a header file that it has never seen, even if it has the path to it.
>
> Jamie
>
>
> On 5/6/07, Hadron <hadronquark@...> wrote:
>>
>>
>> (1) Persistence of semantic completion.
>>
>> If I add this line to some C
>>
>> struct fstab fs;
>>
>> and then try to complete "fs.", it doesn't work. This is fine. So I add
>>
>> #include <fstab.h>
>>
>> Still doesnt complete "fs.". OK, so I visit the file. Bingo! Completion
>> now works. So far as I expected.
>>
>> I then do a semanticdb-save-all-db. So why doesnt it remember the
>> fstab.h completion candidates the next time I open my test file and try
>> to complete "fs."? What does the save function actually save?
>>
>> (2) semantic search
>>
>> There is a blur in my mind between tags and semantic search. Can someone
>> explain how & what the differences are.
>>
>> If I have a few files open, cant I use a semantic search to locate a
>> varable definition? At the moment I use cscope for that. So whats the
>> use of the semantic search functions? They appear to be no more than in
>> "in buffer" search. Does semantic offer a "jump to definition"
>> functionality similar to cscope?
>>
>> thanks for any explanations and/or pointers.
>>
>>
>> --
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/
>> _______________________________________________
>> cedet-semantic mailing list
>> cedet-semantic@...
>> https://lists.sourceforge.net/lists/listinfo/cedet-semantic
>>
>

--

Hi,

  Thanks for your example.  I use a relatively vanilla cedet install
procedure in my .emacs file with my development version of CEDET
active.  At this time, I don't have many active changes over what is
in CVS.  I did the following:

1) Start a fresh emacs
2) Put your sample in /tmp/test.cpp
3) Used M-x semantic-analyze-possible-completions  on the two
   lines you indicated.  I did not get completions.
4) M-x semanticdb-create-ebrowse-database RET /usr/include/ RET
   (This took a little while to finish.
5) Verified that completions are listed correctly on the two lines you
   indicated.

  You should be able to do the same.

  I'm using Emacs 22 from CVS from a couple months back.  Ebrowse had
changed a little between that and Emacs 21.  Hopefully the semantic
code will work between those two versions.

Eric


>>> Hadron <hadronquark@...> seems to think that:
>
>Just while on the subject and Jamie is involved, here is my biggest
>issue at the moment with regard to paths and selective parsing. In the
>following "joke/testbed code" notice 
>
>1) inclusion of fstab.h. This is in /usr/include.
>2) the inclusion of <asm/thread_info.h>. This is in
>~/programming/c/linux.....
>
>All files have been "cscope'd" for easy file opening from structure references.
>
>I open my test file and move to the line "pfstabEntry->". I try inline
>completion. I do not get the structure values. I open the
>/usr/include/fstab.h using cscope navigation command, and *then*
>completion works. Semantic is now aware of fstab.
>
>However, if I move to the "pti->" line having opened the thread_info.h
>file in a similar way, then completion does not work. I know this is
>going to be down to some path issue, but I tried Jamie's suggestion
>earlier specifying the complete directory as well as header root for the
>thread_info file in the c-mode-hook e.g
>
>,----
>| (defun semantic-c-mode-hook ()
>| (semantic-add-system-include "/home/programming/c/linux-source-2.6.20/include/asm"))
>| (add-hook 'c-mode-common-hook 'semantic-c-mode-hook)
>| (add-hook 'c-mode-hook 'semantic-c-mode-hook)
>`----
>
>
>C test Code below.
>
>
>#include <stdio.h>
>#include <stdlib.h>
>#include <fstab.h>
>#include <gtk/gtk.h>
>#include <sched.h>
>#include <asm/thread_info.h>
>
>#include "filesystems.h"
>
>/* START GLOBALS */
>/* The head of the fstab copies */
>GList * pfstab;
>struct fstab * pfstabEntry = p;
>struct thread_info * pti;
>/* END GLOBALS */
>
>
>/* release all memory reserved for a temporary fstab structure */
>void fstabFreeEntry(gpointer p, gpointer ignore){
>	pti->
>	pfstabEntry->
>	g_free(pfstabEntry->fs_spec);
>	g_free(pfstabEntry->fs_file);
>	g_free(pfstabEntry->fs_vfstype);
>	g_free(pfstabEntry->fs_);
>	g_free(p);
>}
>
  [ ... ]

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

>>> Hadron <hadronquark@...> seems to think that:
>
>When debugging a c program, cedet/semantic insists on trying to complete
>things dont need completing. A bit of a pain as it opens a buffer listin
>completion candidates. If the cursor is on a variable called "x" then it
>tries to complete with any other thing beginning with "x" ....
>
>A nice idea would be to only consider completing if something has
>actually been typed on that object/variable in the past few seconds and
>the cursor is at the end and not the start of a completion candidate.
  [ ... ]

You should consider disabling semantic-idle-completions-mode and
instead bind semantic-complete-self-insert to something like "." or
some alpha-numeric characters.  Alternately, you can bind
semantic-complete-analyze-inline to some arbitrary key sequence, like
C-TAB, C-M-TAB, or whatever to call it up on demand.

If you find a patter that works for you, let the list know.  I'm
always looking for a better way to expose this stuff.

Thanks
Eric

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

Hi,

  It would be helpful if you subscribed to the cedet-semantic mailing
list so your email doesn't get quarantined.  Thanks.

  I just checked, and the C++ code:

------
class class3 {

  class3& operator^= (const class3& something);

};
------

Produces the following output for the operator:

-------
 Methods: class3 ^= (something)

or, the short UML version:

 +^= : class3

-------

so semantic is outputting methods for these operators.  I tested using
the version of CEDET in CVS, which is very close to CEDET 1.0pre3.

You can see how semantic thinks about your tag by putting the cursor
on the line you care about and using:

M-x semantic-test-all-format-tag-functions RET

If something shows up incorrectly there, then you can report that
special syntax to the mailing list and I (or you) can try to fix the
parser.

Thanks
Eric


>>> "Matthias Pfeifer" <mpfeifer77@...> seems to think that:
>Hi there,
>
>I am just giving ecb a try and was editing some sourcefiles when i
>found that some operators are handled strangely in the "ECB
>methods-buffer". When i edit my header Vec3D.hpp three of them
>(operators) are listed under "Attributes" (just above "float eps;" and
>"float xyz") and in the Vec3D.cpp they are listed as "Variables".
>
>I don't see the sense in this categorization and doubt my usage of the
>software (ecb)... Am i doing wrong?? I use a current version from cvs
>(emacs also from cvs). Semantic is working and also from cvs.
>
>Also i would like to have operator+ displayed in the methods buffer
>instead of just "+". Is that possible? How please.. i didnt find
>anything...
>
>Thank you.
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by DB2 Express
>Download DB2 Express C - the FREE version of DB2 express and take
>control of your XML. No limits. Just data. Click to get it now.
>http://sourceforge.net/powerbar/db2/
>_______________________________________________
>cedet-semantic mailing list
>cedet-semantic@...
>https://lists.sourceforge.net/lists/listinfo/cedet-semantic
>

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

I don't know what linux C mode is, but it seems to be taking over your
usual c-mode.  Using:

C-h f linux-c-mode RET

will help you find it, and read about why it's there.

Eric

>>> Hadron <hadronquark@...> seems to think that:
>"Eric M. Ludlam" <eric@...> writes:
>
>>>>> Hadron <hadronquark@...> seems to think that:
>>>
>>>When I try to create my system db, I keep seeing 
>>>
>>>"ignoring unknonwn mode 'linux-c-mode'"
>>>
>>>in the status bar as it parses the files. Finally it just crawls to a
>>>halt and stops.
>>>
>>>I pointed it to my /usr/src/linux/include directory having removed all
>>>non 386 headers.
>>>
>>>Any tips?
>>>
>>>(cvs cedet, emacs snapshot)
>>   [ ... ]
>>
>> You likely need a hook that looks like this for linux-c-mode:
>>
>> (add-hook 'linux-c-mode-hook 'semantic-default-c-setup)
>>
>> Look into linux-c-mode to get the name of the hook function.
>
>What is linux-c-mode? There is no mention of it in my code or via the
>help system.
>
>The only "linux" thing I have is
>
>  (c-set-style "linux")
>
>
>>
>> Eric
>

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

"Eric M. Ludlam" <eric@...> writes:

>>>> Hadron <hadronquark@...> seems to think that:
>>
>>When I try to create my system db, I keep seeing 
>>
>>"ignoring unknonwn mode 'linux-c-mode'"
>>
>>in the status bar as it parses the files. Finally it just crawls to a
>>halt and stops.
>>
>>I pointed it to my /usr/src/linux/include directory having removed all
>>non 386 headers.
>>
>>Any tips?
>>
>>(cvs cedet, emacs snapshot)
>   [ ... ]
>
> You likely need a hook that looks like this for linux-c-mode:
>
> (add-hook 'linux-c-mode-hook 'semantic-default-c-setup)
>
> Look into linux-c-mode to get the name of the hook function.

What is linux-c-mode? There is no mention of it in my code or via the
help system.

The only "linux" thing I have is

  (c-set-style "linux")


>
> Eric

--

Hi,

  You should subscribe to the mailing lists so that your email doesn't
get quarantined.

  The ebrowse support for CEDET is described in the application
developers guide in the semantic DOC directory.

If it throws an error, please use:

M-x toggle-debug-on-error RET

to turn on stack traces, and send the output.  I've had trouble
keeping it working across different versions of Emacs, so that may be
related.

Thanks
Eric

>>> Hadron <hadronquark@...> seems to think that:
>"Eric M. Ludlam" <eric@...> writes:
>
>>>>> Hadron <hadronquark@...> seems to think that:
>>>
>>>In the following code,
>>>
>>>
>>>		struct fstab * pCopy = g_malloc(sizeof(struct fstab));
>>>         
>>>		pCopy->fs_spec=g_strdup(pfstabEntry->fs_spec);
>>>                /*snip*/
>>>		pCopy->
>>>		
>>>		fstab f;
>>>
>>>Why does pCopy-> not allow proper completion of the fstab structure
>>>members? I have opened the relevant header.
>>   [ ... ]
>>
>> The definition of the fstab needs to be in a searchable database
>> somewhere.  You might be able to use
>> `semanticdb-create-ebrowse-database' and point it at the directory
>> where fstab is (/usr/include/whatever...) to get it working.
>
>What is ebrowse?  I thought that was for c++? There is no mention of it
>in the docs I read for setting up semantic for completion. I thought
>that was what the project directory roots were for?
>
>Can you reference the online docs for this please and I will re-read.
>
>> If ebrowse doesn't have the right info in it, then
>> `semanticdb-create-system-database' against that dir (as you tried
>> earlier) should get it working.
>
>"apply: Wrong type argument: number-or-marker-p, nil"
>
>
>>
>> If those don't get it working, you can start debugging the semantic
>> search path with `semantic-adebug-searchdb'.  Those results will help
>> me debug additional problems.
>>
>> Good Luck
>> Eric
>

"Eric M. Ludlam" <eric@...> writes:

>>>> Hadron <hadronquark@...> seems to think that:
>>
>>In the following code,
>>
>>
>>		struct fstab * pCopy = g_malloc(sizeof(struct fstab));
>>         
>>		pCopy->fs_spec=g_strdup(pfstabEntry->fs_spec);
>>                /*snip*/
>>		pCopy->
>>		
>>		fstab f;
>>
>>Why does pCopy-> not allow proper completion of the fstab structure
>>members? I have opened the relevant header.
>   [ ... ]
>
> The definition of the fstab needs to be in a searchable database
> somewhere.  You might be able to use
> `semanticdb-create-ebrowse-database' and point it at the directory
> where fstab is (/usr/include/whatever...) to get it working.

What is ebrowse?  I thought that was for c++? There is no mention of it
in the docs I read for setting up semantic for completion. I thought
that was what the project directory roots were for?

Can you reference the online docs for this please and I will re-read.

> If ebrowse doesn't have the right info in it, then
> `semanticdb-create-system-database' against that dir (as you tried
> earlier) should get it working.

"apply: Wrong type argument: number-or-marker-p, nil"


>
> If those don't get it working, you can start debugging the semantic
> search path with `semantic-adebug-searchdb'.  Those results will help
> me debug additional problems.
>
> Good Luck
> Eric

--

"Eric M. Ludlam" <eric@...> writes:

>>>> Hadron <hadronquark@...> seems to think that:
>>
>>I think the INSTALL instructions are incorrect in the CVS version.
>>
>>I had to 
>>
>>,----
>>| (setq semantic-load-turn-everything-on t)
>>| (load-file "~/lisp/cedet/common/cedet.el")
>>| (semantic-load-enable-guady-code-helpers)
>>`----
>>
>>to get senator mode on for c files whereas the INSTALL file says only
>>
>>,----
>>| ;; Load CEDET
>>| (load-file "~/cedet-VERSION/common/cedet.el")
>>| 
>>| ;; Enabling various SEMANTIC minor modes.  See semantic/INSTALL for more ideas.
>>| ;; Select one of the following:
>>| 
>>| ;; * This enables the database and idle reparse engines
>>| ;;(semantic-load-enable-minimum-features)
>>| 
>>| ;; * This enables some tools useful for coding, such as summary mode
>>| ;;   imenu support, and the semantic navigator
>>| (semantic-load-enable-code-helpers)
>>| 
>>| ;; * This enables even more coding tools such as the nascent intellisense mode
>>| ;;   decoration mode, and stickyfunc mode (plus regular code helpers)
>>| ;; (semantic-load-enable-guady-code-helpers)
>>| 
>>| ;; * This turns on which-func support (Plus all other code helpers)
>>| ;; (semantic-load-enable-excessive-code-helpers)
>>| 
>>| ;; This turns on modes that aid in grammar writing and semantic tool
>>| ;; development.  It does not enable any other features such as code
>>| ;; helpers above.
>>| ;; (semantic-load-enable-semantic-debugging-helpers)
>>`----
>>
>>Can someone verify?
>
> Hmmm.  I'm not familiar with that problem.  Perhaps if you use the
> sample from the install file, you could start with --debug-init and
> some error is preventing a full run through your .emacs file.

Simply install from cvs, remove all other references for cedet. Follow
the instructions in the INSTALL file. Doesn't work - I will double check
I didnt screw up later when I have time. It is just a documentation
issue as detailed above I think.

>
>
>>In addition, if I try
>>
>>semantic-complete-analyze-inline
>>
>>I get:
>>
>>eieio-oref: Wrong type argument: (or object-p class-p), nil
>>
>>in my *message* buffer.
>
> Try:
>
> M-x toggle-debug-on-error RET
>
> then re-run.  The stack will help me figure out what's going on.
>
>>The pop up menu showing completions doesnt work for - it just flickers
>>wildly. emacs-snapshot GNU Emacs 22.0.99.1 (i486-pc-linux-gnu, GTK+
>>Version 2.10.11) of 2007-05-01 on pacem, modified by Debian.
>
> I've seen the popup flicker on occasion as well.  When I went to look
> into it, it went away, so I still don't know what causes it.

I found out what it was for me - it was a clash with rdictcc. Toolbar
popups are relatively useless in emacs 22 that I use anyway since you
cant select with the toolbar. I do the "Inline" completion just fine.

>
>>Are there any walkthroughs/tutorials anyhwere on how to use this stuff
>>as it seems quite useful. 
>   [ ... ]
>
> This is an area for improvement for CEDET.

I dont want to be a "whiner" but the CEDET page really needs pruning. It
is really confusing - too many old versions, too much confusion betwene
cedet versions and semantic, too man pre-release v debug versions, too
many sets of instructions for different version IMO. Keep it all in the
INSTALL file in the tar files themselves would be my sage advice :-;

>
> Eric

Many thanks for the reply.

--