<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'>Hi,<br>This is very helpful.<br>I did as the course 220a blog description suggested and created a directory with symlink to clm-4 inside it, then copied v.ins from clm-4 to that directory.<br><br>I'm running emacs from that directory and saved an .emacs file in there too, which looks like this:<br><br>;;slime<br>(setq inferior-lisp-program "/usr/bin/sbcl")<br>(add-to-list 'load-path "/usr/share/slime")<br>(require 'slime)<br>(slime-setup)<br>(add-to-list 'auto-mode-alist '("\\.ins$" . lisp-mode))<br><br>...so M-x works and slime is loading from emacs.<br><br>(compile-file "v.ins") works in slime-repl sbcl, and I get a v.fasl etc.<br><br>but<br><br>(load "v") bumps me out to the debugger, and this is where I'm stuck with clm since the blog description is about cm, not clm. I also looked at the readme.clm. Not sure about the .ins-buffer part you described, below.<br><br>Just not sure what I'm missing to get thru (load "v"), and on to (with sound ()...). Perhaps I should be running emacs directly from the clm-4 source folder?<br><br>Regards,<br>Jim Hearon<br><br><br><div>> From: cmdist-request@ccrma.Stanford.EDU<br>> Subject: Cmdist Digest, Vol 62, Issue 3<br>> To: cmdist@ccrma.Stanford.EDU<br>> Date: Tue, 25 Jun 2013 12:00:03 -0700<br>> <br>> Send Cmdist mailing list submissions to<br>> cmdist@ccrma.stanford.edu<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist<br>> or, via email, send a message with subject or body 'help' to<br>> cmdist-request@ccrma.stanford.edu<br>> <br>> You can reach the person managing the list at<br>> cmdist-owner@ccrma.stanford.edu<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of Cmdist digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. clm, slime (James Hearon)<br>> 2. Re: clm, slime (andersvi@notam02.no)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Tue, 25 Jun 2013 01:33:32 +0000<br>> From: James Hearon <j_hearon@hotmail.com><br>> Subject: [CM] clm, slime<br>> To: "cmdist@ccrma.Stanford.EDU" <cmdist@ccrma.Stanford.EDU><br>> Message-ID: <BLU168-W1033F86143A00351545FF08E58B0@phx.gbl><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> Hi,<br>> Getting myself confused trying to interact with clm (clm-4) using emacs and slime.<br>> <br>> I have f18, sbcl, clm-4 and was doing fine from command line with:<br>> <br>> (load "all.lisp")<br>> (compile-file "v.ins")<br>> (load "v")<br>> (with-sound () (fm-violin 0 1 440 .1))<br>> <br>> But found I needed more REPL to feel comfortable working, so I yum installed emacs and then slime.<br>> <br>> Not sure how to inteact with clm using slime from emacs now.<br>> <br>> I read the Clementson's Blog post about course 220a, but that covers mostly slime and cm. For cm, I'm doing fine on f18 using Grace, and S7.<br>> <br>> I would just like to interact with clm from slime for instrument building, testing etc.<br>> <br>> Is there some info on this, or have I misunderstood and am totally going the wrong way with this?<br>> <br>> Thanks,<br>> <br>> <br>> <br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: http://ccrma-mail.stanford.edu/mailman/private/cmdist/attachments/20130625/c5d323af/attachment-0001.html <br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Tue, 25 Jun 2013 10:34:48 +0200<br>> From: andersvi@notam02.no<br>> Subject: Re: [CM] clm, slime<br>> To: cmdist@ccrma.Stanford.EDU<br>> Message-ID: <87r4fqh9lj.fsf@notam02.no><br>> Content-Type: text/plain<br>> <br>> <br>> J> I would just like to interact with clm from slime for instrument<br>> J> building, testing etc.<br>> <br>> J> Is there some info on this, or have I misunderstood and am<br>> J> totally going the wrong way with this?<br>> <br>> Youre definitely not on a wrong path. Slime provides extremely powerful<br>> interaction for everyting common-lispy, also sbcl/clm.<br>> <br>> First make sure slime is set up and running. If 'M-x slime' gets sbcl<br>> running and gives you a *slime-repl* buffer you should be fine.<br>> <br>> For clm, you'll need to have your .ins files in lisp-mode when editing.<br>> Putting:<br>> <br>> (add-to-list 'auto-mode-alist '("\\.ins$" . lisp-mode))<br>> <br>> inside .emacs will make emacs do this for you.<br>> <br>> In clm, the standard mode is working on a separate instrument file -<br>> <br>> (definstrument ...<br>> (run ...))<br>> <br>> compiling and loading it, fex. by hitting "C-c C-k" inside the<br>> .ins-buffer in slime, or following the example about v.ins in<br>> README.clm.<br>> <br>> Then calling it from a score:<br>> <br>> (with-sound (various-file-options)<br>> (instrument-call 1)<br>> (instrument-call 2)<br>> ...)<br>> <br>> But here the repl isnt very useful. Usually you dont spend much time<br>> coding in the 'slime-repl* buffer when working on larger bits of code,<br>> eg. instruments or score-files.<br>> <br>> Instead you typically set up files in lisp-mode (.cl, .clm or somesuch)<br>> to hold variations and sketches, projects etc., moving around in these,<br>> evaluating regions or expressions. Here slime comes in with all its<br>> powers, giving you auto-completion, cross-referencing,<br>> documentation-lookup, editing expressions, evaluation of regions,<br>> looking up arglists etc.<br>> <br>> You could read the basic slime-docs from a info-file or similar. Or<br>> have a look in the various menus.<br>> <br>> Good luck finding your ways around.<br>> <br>> -anders<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> _______________________________________________<br>> Cmdist mailing list<br>> Cmdist@ccrma.stanford.edu<br>> http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist<br>> <br>> <br>> End of Cmdist Digest, Vol 62, Issue 3<br>> *************************************<br></div> </div></body>
</html>