Quesstion about Alt-. navigation to function definitions

Jeff Cunningham jeffrey at jkcunningham.com
Mon Oct 28 01:25:05 UTC 2013


On 10/27/2013 12:06 AM, Helmut Eller wrote:
> On Sat, Oct 26 2013, Jeff Cunningham wrote:
>
> [...]
>> Is there any remedy for this? Using grep to move around works but is
>> annoyingly cumbersome and time consuming.
> I don't see any obvious problem with the bits you posted and without a
> reproducable test case it's hard to say what the actual problem is.
>
> One problem could be that you have some declaration/proclamation
> somewhere, e.g. (proclaim '(optimize (debug 0))).  If you're using SBCL
> and debug is 0 then SLIME can't find the definition for a name.  I have
> (proclaim '(optimize (debug 2))) in my .sbclrc and that seems to work
> quite OK.
>
> Another cause could be that you load the source and not the fasl file.
> M-. does typically not work so well for non-compiled functions.
>
> Yet another problem could be that there is no IN-PACKAGE form in the
> file so that SLIME searches in the wrong package. (That's unlikey, tho,
> as compiling an individual function seems to work.)
>
> In general, M-. seems to be used by many people therefore I think we
> would note regressions on our side pretty quickly.
>
> Helmut
Thanks for the response, Helmut. I was hoping there was something I was 
missing.

I don't normally change the optimization in development code. But I went 
ahead and tried the proclaim '(optimize (ebug 2))) in my .sblcrc as you 
suggested, but that made no difference.

All my source files have (in-package 'ftis-v43), the package defined in 
the package.lisp file.

I'm guessing it has something to do with not loading local fasl files, 
because if I open each of the lisp sources and compile fasls for them 
with Ctrl-c, k I can then navigate around with Alt-.   But I still have 
to compile the files manually. Simply loading via ASD leaves it in a 
state where it can't navigate.

On the other hand, i can put the point on a function from an inluded 
package, say something like cl-ppcre:scan and it will go off and find 
that just fine.

There's something I'm missing.

--Jeff



More information about the slime-devel mailing list