unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
* semantic/senator auto complete
@ 2007-05-08  8:16 Hadron
  0 siblings, 0 replies; only message in thread
From: Hadron @ 2007-05-08  8:16 UTC (permalink / raw)
  To: help-gnu-emacs


I realise there is a mailing list, but it is very quiet and I am hoping
someone here can help now.

I have a small sample C file "bug.c"

,----
| #include <fstab.h>
| int  main()
| {
| 	fstab fedora;
| 	fedora.
| }
`----

If I open "fstab.h" in emacs then by placing the cursor at the end of
"fedora." then I get valid completions. I have then issued the command
"semanticdb-save-all-db". In the local directory there is now a
"semantic.cache" file with the following in:

,----
| ;; Object bug/
| ;; SEMANTICDB Tags save file
| (semanticdb-project-database-file "bug/"
|   :tables (list 
|    (semanticdb-table "bug.c"
|     :major-mode 'c-mode
|     :tags '(("fstab.h" include (:system-flag t) (dependency-file "/usr/include/fstab.h") [1 19]) ("main" function (:type "int") nil [20 59]))
|     :file "bug.c"
|     :pointmax 60
|     :unmatched-syntax 'nil
|     )
|    )
|   :file "semantic.cache"
|   :semantic-tag-version "2.0"
|   :semanticdb-version "2.0"
|   )
`----

My question is : how do I get semantic to open & parse the cache file
properly in my next emacs session when I open bug.c? I have to manually
open "fstab.h" in order to get completions to work for the types it
contains. So what job is the cache doing? Is it not possible to get
completion without manually opening each and every file?

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2007-05-08  8:16 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-08  8:16 semantic/senator auto complete Hadron

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).