Hooray, That was what I was missing. re: Did you load clm first? Eg. (load "/my/dir/clm/all.lisp") ? ...so am off to try to build an inst with clm now. Regards,Jim Hearon
> Message: 1 > Date: Sat, 29 Jun 2013 14:20:32 +0200 > From: [email protected] > Subject: Re: [CM] Cmdist Digest, Vol 62, Issue 3 > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain > > >>>>> "J" == James Hearon writes: > > J> (compile-file "v.ins") works in slime-repl sbcl, and I get a v.fasl > etc. > > J> but > > J> (load "v") bumps me out to the debugger, and this is where I'm > J> stuck with clm since the blog description is about cm, not clm. > > Did you load clm first? Eg. (load "/my/dir/clm/all.lisp") ? > > Quick tip, you'll always hit errors working with code. Just telling > somebody you hit an error is useless without the backtrace (messages, > everything which leads up to the error, including the error-messages > etc). > > Working w. slime you'll typically look in a *sldb-xxxx* buffer (which > pops up) for errors, and *slime-repl* and *inferior-lisp* for warnings. > > -anders
_______________________________________________ Cmdist mailing list [email protected] http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist
