OK, you can now get around this bug by evaluating this. I don't think
I'll check it in, however. I think I'll just enforce the fact that
jde-xref-store-prefixes must be populated.If I don't, people may
not even use it, and then they might complain the making the xref db
is taking long or using a lot of memory.
(defun jde-xref-find-or-create-package-in-cache (package)
(unless jde-xref-db-base-directory
(error The variable `jde-xref-db-base-directory' must be specified to load the
xref db))
(if (file-exists-p (jde-xref-get-caller-file package))
(or (jde-xref-find-package-in-cache package jde-xref-cache)
;; Or we need to get the new package and put it in the cache
(let ((data (jde-xref-load-package-hashes package)))
(setq jde-xref-cache (cons (cons package data)
(if ( (length jde-xref-cache)
jde-xref-cache-size)
(cdr jde-xref-cache)
jde-xref-cache)))
data))
(jde-xref-create-package-hashes t)))
Andrew Hyatt [EMAIL PROTECTED] writes:
This probably is a bug. I recommend you keep this variable populated,
though, but in the meantime I'll look into it.
Schmitt, Christian (ext.) [EMAIL PROTECTED] writes:
Hi,
I've been trying to get the new xref stuff in JDEE to work.
When looking at the doc string for the variable jde-xref-store-prefixes
it says:
Documentation:
A list of what prefixes to put in the database. A value of NIL
indicates that to store everything (this will include which
functions call java functions like println, etc.) Otherwise, it is
a list of prefixes such as: '(org jde), to keep track of all
references to classes that start with org or jde.
So I thought I'll leave the variable set to NIL and all should be OK.
But (so far) I've only got results from (e.g.) jde-xref-display-call-tree
when jde-xref-store-prefixes is not NIL but set to the top level
directory in my package tree.
Is this a bug in the xref code or only in the doc string?
Thanks,
Christian Schmitt
