[slime-devel] Re: xref issue

Carlos Konstanski ckonstanski at pippiandcarlos.com
Sat Aug 16 18:49:42 UTC 2008


Carlos Konstanski writes:
 > On Thu, 14 Aug 2008, Tobias C. Rittweiler wrote:
 > 
 > > Date: Thu, 14 Aug 2008 18:34:33 +0200
 > > From: Tobias C. Rittweiler <tcr at freebits.de>
 > > To: slime-devel at common-lisp.net
 > > Subject: [slime-devel] Re: xref issue
 > > 
 > > Carlos Konstanski <ckonstanski at pippiandcarlos.com> writes:
 > >
 > >> I should add that this only happens when the symbol is a method name.  Normal
 > >> functions are found just fine.
 > >
 > > It works for me just fine in Emacs 23.x, 22.1.1, and 21.x with SBCL, for
 > > functions, generic-functions, and macros.
 > >
 > >  -T.
 > 
 > I cannot look into it more right now because I am at work.  But later I
 > will dig into this deeper, starting with the easy thing: CVS updates by
 > date to find when it changed.  I will also try with emacs 23.  I want
 > to use the gentoo ebuild, but I cannot do CVS checkouts from work
 > because of firewall rules (emacs-23 is a CVS ebuild).
 > 
 > I did also notice that M-. now DOES work for finding labels.  This is
 > great!
 > 
 > Carlos Konstanski
 > _______________________________________________
 > slime-devel site list
 > slime-devel at common-lisp.net
 > http://common-lisp.net/mailman/listinfo/slime-devel

OK, I found that a 2008-08-08 checkout works, while a 2008-08-09 one
does not.  This is true of both emacs 22.2 and 23 CVS.  I also tested
on three separate computers: two amd64 boxes and one x86 box.  I think
the problem occurs when an XREF buffer is involved; finding flets
works fine in the 2008-08-08 version.

Next step: I will look at the code, and try to find out what is going
wrong when the following occurs (I suspect `standard-output' does not
contain a valid buffer name):

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  set-buffer(nil)
  (save-current-buffer (set-buffer standard-output) (prog1 (progn ... ... ... ... ...) (assert ...) (setq buffer-read-only t)

It is always possible that an external variable is affecting the
functionality.  Remember my last issue, which turned out to be wholly
araneida's fault?  Here are my slime settings in .emacs.  Could any of
these have an effect?

 '(slime-autodoc-mode t)
 '(slime-autodoc-use-multiline-p t)
 '(slime-compilation-finished-hook (quote (slime-maybe-list-compiler-notes slime-maybe-show-xrefs-for-notes)))
 '(slime-complete-symbol-function (quote slime-fuzzy-complete-symbol))
 '(slime-kill-without-query-p t)
 '(slime-multiprocessing t)
 '(slime-repl-history-size 9999)
 '(slime-repl-return-behaviour :send-only-if-after-complete)
 '(slime-startup-animation nil)
 '(slime-truncate-lines nil)
-- 
Carlos



More information about the slime-devel mailing list