On 05/21/2012 09:16 PM, Clint Hui wrote:
> Mitchel Humpherys<mitch.special<at> gmail.com> writes:
>> You, sir, are amazing. Works like a charm.
>> Thanks again for this amazing tool!
> Hey, Mitchel:
> I am facing the same problem here, after digging into those caches files that
> you suggested, I couldn't find any escaped characters that were in you case. So
> how did you fix your problem in the end, I didn't quite get it from the
> conversation. Thanks, also, how did you solve this?
> It seems like it never "remembers" things it has already parsed (I have to re-
> parse includes each time I open emacs), which makes it a bit sluggish.
> I am bothered by this too. Thank you a ton
There are a couple possibilities for semanticdb not loading in old
semanticdb save files.
One is if the security for the save file is somehow getting in the way.
If that is the case, check your *Messages* buffer after you think the
database should have been loaded to see what it says. The messages
would be explicit about a 'corrupt' file.
If it were corrupt, or if the version numbers were broken (and it thinks
your save files are too old) it should save over the old file when it
reparses your headers and you exit emacs. You can configure it to not
save, and if you did that, use the semanticdb-save-add-db command to
Since the saved databases are just lisp code, you can open them up, and
use: C-M-f to do a quick check for unbalanced parenthesis (or escape
Lastly, if your headers are on some path accessible via tramp or one of
the network prototcols in Emacs, it won't save those.
If you are using the default setup, then it is likely you have something
in your headers causing the save file to go bad. If just scanning with
C-M-f doesn't work, you could use edebug (just load it) and then use
eval-buffer to see if anything goes wrong, and that could point at the