I’ve been a Lisp nut for years. I was first exposed to Lisp on my TRS-80, when I was about thirteen; Randy Beer had written a Lisp introduction in the March ’83 issue of 80 Micro, and I remember reading it again and again. I’ve used various flavors of Lisp for exploratory prototyping programming over the years, and have enjoyed using both Scheme and Common Lisp.
Built in interface to Tk widget system. Allows a mixture of tcl and common lisp to be used in a user interface-your choice which you use. History GCL is the product of many hands over many years. The original effort was known as the Kyoto Common Lisp system, written by Taiichi Yuasa and Masami Hagiya in 1984.
- Removes the Paper image from Layouts – LAYOUTELEM.lsp. Utility for editing the color of elements in the interface – UIcolor.lsp. Creates a set of numbers at user specified start / increment / distance – AN.LSP. Allows user to adjust the radius of multiple circles by a value or factor – CHRAD.LSP.
- My office computer change to mac.OS.So all of my lisp programs do not support it. Can you give me some ideas to change lisp codes to run with mac.
- Hello, I have recently moved from Windows to Mac for production in AutoCAD. Everything was working smoothly until I came across a.lsp that I would absolutely need to be efficient. The PROBE.lsp that I have been for years allows me to turn off/freeze specific layers in an xref, which I use d.
Getting a dialect of Common Lisp running on Mac OS X isn’t hard — in fact, if you’re just setting out, an excellent choice is LispWorks Personal Edition. I’ve recently gotten to the point, however, where I’ve wanted to do some work with the Common Lisp Interface Manager, which isn’t supported in LispWorks Personal Edition under Mac OS X, and set out to configure a Common Lisp installation on my MacBook from the ground up.
It wasn’t difficult, although it took some Googling to get all the pieces together; shortly after I finished, someone on the Bay Area Functional Programmer‘s mailing list asked about running Common Lisp on Mac OS X, and I put together my notes on the topic and replied. The list is fairly small — less than 300 members — and I promised them and myself that I’d organize the notes and provide them in a more accessible location.
What follows is a step-by-step installation guide to installing Steel Bank Common Lisp (SBCL) and McCLIM on a PowerBook G4; I undertook this from the initial notes I took configuring the MacBook. I chose SBCL because it’s well-supported by the open source community and works well with McCLIM; I have nothing against other Common Lisp implementations, including Clozure.Â
A word of warning is in order: I’m comfortable with Common Lisp, but relatively unfamiliar with how Common Lisp programmers handle package distribution. I get the basic idea behind ASDF, of course, but I’m not seasoned in its use. Consequently, I had a get-things-working-and-clean-up-later mentality when I undertook my first SBCL-McCLIM configuration, and this largely remained when I wrote what follows. Other Lisp developers may have better ways to organize their working environments, and I’d welcome positive comments (drop me an email, and we’ll figure out how to incorporate your feedback).
Starting out, you should have a relatively up-to-date Mac OS X box (I’ve done this on Mac OS X 10.4.x and 10.5.x systems). When you’re done, you will have installed Carbon Emacs, SLIME, SBCL, and McCLIMÂ configured to work with the X Windows server Mac OS X provides, along with darcs.Â
Carbon Emacs on Mac OS X provides you with an Emacs instance running as a Mac OS X application. I like it for general editing, as well as the obvious purpose of giving me a place to run SLIME and do my Lisp development.
- Get Carbon Emacs from its home page. If you need a version for a version of Mac OS X other than 10.5, check here.
- Mount the disk image you download, and copy Emacs.app to your Applications folder.
Steel Bank Common Lisp
- Download SBCL. Choose either X or P on this page for the X86 or PPC build, respectively.
- Unpack the distribution, and open a Terminal to the directory where you’ve unpacked the distribution.
- Install per the INSTALL instructions. I used the default options, placing SBCL in /usr/local by issuing:
Ccleaner Mac Os X
At this point in time, you should be able to run SBCL from the shell.
SLIME in Carbon Emacs is swell.
- Download SLIME. I used CVS in the terminal, stashing the whole thing in a hidden directory. If you use a lot of emacs packages, you may well already have a directory for them, and you can put SLIME there as well.
- Wire SLIME up to your emacs installation. I followed the instructions in the SLIME documentation.
In a nutshell, it says to add the following to your ~/.emacs:Â Â Â Â
/usr/local/bin/sbcl is the path to SBCL you specified in the previous section, and
~/.slime is the path to the slime directory you specified in the previous step.
You can stop at this point if you don’t want to work with McCLIM; you have a working SBCL
environment using Carbon Emacs and SLIME. To use SLIME, start emacs from the Terminal or
Carbon Emacs and run SLIME using M-x slime.
Some of the stuff you need for McCLIM is kept in a darcs repository, so you first need to get and install darcs. I used one of the pre-built binaries. Make sure that however you do this, darcsÂ is in your path when you’re done installing, of course.
I followed these stepsÂ Â to build and configure McCLIM from source.
- You’re going to use ASDF to get various Common Lisp packages, and you need a place to put the resulting files, as well as to tell SBCL where that place is.Â Make a directory ~/lispsystems in your home directory, and configure SBCL by adding the following to your ~/.sbclrc file:
- Fetch the McCLIM sources.
- Fetch McCLIM’s dependencies: the Common Lisp Library for X, spatial-trees, and flexichain:
- Build the McCLIM system. Fire up Carbon Emacs, run SLIME using M-x slime, and enter:
Be prepared to wait a while as the system builds for the first time.Â
- To see if everything works as expected, you can build the samples:
- To play with the samples:
You also have the option of getting McCLIM using clbuild, as this pageÂ describes. That worked for me under Mac OS X 10.5, but did not under Mac OS X 10.4, and I didn’t bother to investigate what was different.Â
Good luck and happy hacking!