<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><div>Hooray,</div><div><br></div><div>That was what I was missing.</div><div><br></div><div>re: <span style="font-size: 12pt;">Did you load clm first? Eg. (load "/my/dir/clm/all.lisp") ?</span></div><div><br></div><div>...so am off to try to build an inst with clm now.</div><div><br></div><div>Regards,</div><div>Jim Hearon</div><br><div><br>> Message: 1<br>> Date: Sat, 29 Jun 2013 14:20:32 +0200<br>> From: anders.vinjar@bek.no<br>> Subject: Re: [CM] Cmdist Digest, Vol 62, Issue 3<br>> To: cmdist@ccrma.Stanford.EDU<br>> Message-ID: <871u7lglbj.fsf@notam02.no><br>> Content-Type: text/plain<br>> <br>> >>>>> "J" == James Hearon writes:<br>> <br>> J> (compile-file "v.ins") works in slime-repl sbcl, and I get a v.fasl etc.<br>> <br>> J> but<br>> <br>> J> (load "v") bumps me out to the debugger, and this is where I'm<br>> J> stuck with clm since the blog description is about cm, not clm.<br>> <br>> Did you load clm first? Eg. (load "/my/dir/clm/all.lisp") ?<br>> <br>> Quick tip, you'll always hit errors working with code. Just telling<br>> somebody you hit an error is useless without the backtrace (messages,<br>> everything which leads up to the error, including the error-messages<br>> etc).<br>> <br>> Working w. slime you'll typically look in a *sldb-xxxx* buffer (which<br>> pops up) for errors, and *slime-repl* and *inferior-lisp* for warnings.<br>> <br>> -anders<br><br></div> </div></body>
</html>