A high-level Common Lisp framework for parallel and distributed programming.


At the moment, Erlisp's homepage is at the author's personal website. There you will find Erlisp's roadmap and other more in-depth information.

Mailing list

The erlisp-devel mailing list is a forum to discuss Erlisp, its development, and its usage. It is also mailed automatically with patch logs whenever a new set of patches is added to the darcs repository.

Thanks to GMANE, the mailing list is also accessible as the newsgroup gmane.lisp.erlisp.devel on The newsgroup is a bi-directional interface to the mailing list, so e-mails sent to either one will show up on both.

Latest snapshot

You can download the latest snapshot of the Erlisp source code here: erlisp-snapshot.tar.gz. Whenever a new patch is checked into the repository, a patch description is sent to the mailing list and the snapshot is updated.

Darcs repository

Erlisp is being developed in the darcs repository at Below are some instructions on working with the Erlisp source code using command-line darcs. More information can be found at the darcs website.

Getting the source

To get Erlisp's source code for the first time, simply do:

$ darcs get

In the current working directory, this will create a subdirectory called erlisp, containing a working copy of the Erlisp repository.

Whenever you want to get the latest updates from the repository, go to this erlisp directory and do:

$ darcs pull

Working with the source

With darcs, there's no difference between a working copy and a repository. So after the above you should have your own private Erlisp repository to do development in. At any time, you can inspect your changes with:

$ darcs whatsnew --summary -l

The -l causes new files that have not been darcs added yet to show up in the listing.
Leave off the --summary to see the actual diffs, instead of just the filenames of changed files.

Whenever you have some changes you are satisfied with, do:

$ darcs record

If this is the first time you do a darcs record, you'll be asked for your e-mail address. You are recommended to use the format "Full Name <e-mail@addr.ess>", for example: SpongeBob SquarePants <>.

You will then be asked which of your changes you want to record in the patch. This is handy to make several coherent patches out of a lot of unrelated changes.

Finally, you'll be asked for a patch name and a longer patch description. (The latter will open your default editor.) Try to give patches a meaningful name, and a description in the style of GNU Change Logs.

After all this, you will have a new local patch. You can now make more changes and patches, unrecord some patches you are not happy with after all, get new patches from the main repository (as described above), and so forth. See the manual at the darcs website for more information.

Sending patches back

If you have a patch (or a set of patches) that you feel should be in the main Erlisp repository, you'll need to e-mail them to me. To do so, start with the following:

$ darcs send -o filename

Darcs wil ask you which patches you want to include, and then writes them out to the file called filename. You should then attach this file to an e-mail and send it to

If you have a command-line e-mail command (like nail or sendmail), you can automate the e-mail sending as follows:

$ darcs send --sendmail-command COMMAND

After you specify the patches to include, darcs should figure out my e-mail address by itself, and then use the specified COMMAND to send the e-mail. For more information about the syntax of COMMAND, and how to set it in your darcs preferences, see the manual at the darcs website.

Back to

Valid XHTML 1.0 Strict