The Ohio State Emacs Lisp Archive

Welcome to the Ohio State Emacs Lisp Archive.

Browse the archive via HTTP Browse the archive via FTP

News:

Lispmeralda - 2001/06/10
The most recent news is that this archive will probably merge with Emacs Lisp List into Lispmeralada. We hope to have something working soon. Thanks for your patience!

Intent to close - 2001/05/02
Well, due to time constraints on my part, I currently plan to close the OSU Emacs Lisp archive as soon as Savannah allows for non-GNU programs. Savannah is a much more advanced technology; it will allow for CVS access, etc. But the archive will remain open until that time, and probably some time after. Feel free to mail your comments about this to walters@cis.ohio-state.edu.

Using the search engine - 2001/01/21
When using the search engine, please keep in mind that it by default only searches the main archive, which is just entries which have been submitted. The "incoming" archive is a lot of Emacs Lisp code that has been collected from various places on the web; it is out of date, and not necessarily organized.

Search engine - 2001/01/20
The search engine is starting to shape up. Further improvements are planned. If you have any suggestions, please feel free to send them to archive@cis.ohio-state.edu.

.zip submissions - 2000/07/30
Multi-file submissions in the form of `.zip' files are now accepted, in addition to `.tar.gz' files.

We are reopening! - 2000/07/10
The OSU Elisp archive is now being actively maintained again! For information on submitting your code to the repository, please see the section Submissions below.

Submissions:

How To Submit Emacs Lisp Code to the Archive

Make sure that your code has a clear copyright statement near the top, with a free software license attached.

We cannot accept code that does not have a copyright. In addition, please use a license that makes your code free software. For an example of acceptable terms, type 'C-h C-c' inside Emacs. If in doubt, send mail to archive@cis.ohio-state.edu.
Please read the section "Tips And Conventions" in the Emacs Lisp manual, and try to make your entry conform as much as possible to these standards. It is not strictly required for submission, however.
Create an Emacs Lisp Archive Entry for your code. For details about the various fields, see here .
- If you are submitting a single .el file, then an ELAE like:
```
;; Emacs Lisp Archive Entry
;; Filename: somefile.el
;; Author: Jane Schmoe <jane@example.com>
;; Version: 1.0
```
  will suffice. Just put it somewhere in your file.
- If you are creating a multi-file entry (for example, if you include Texinfo documentation, or you have multiple .el files), then you should create an ELAE like:
```
;; Emacs Lisp Archive Entry
;; Package: foo
;; Author: Jane Schmoe <jane@example.com>
;; Version: 1.0
```
  and place the ELAE in the most important .el file in your distribution.
  After you have added the ELAE, use the `tar' utility to package your files. The filename should be `<package name>-<version>.tar[.gz]'. Additionally, this archive should unpack into a directory with the same name as the tar archive, but without the 'tar[.gz]' extension (i.e. <package name>-<version>).
  
  For example, the above author could submit her package `foo' as `foo-1.0.tar.gz', which should unpack into a directory named `foo-1.0'.
  
  Alternatively, you may use the `zip' utility to compress your files. The rule about unpacking into a directory of the same subname (i.e. `foo-1.0.zip' should unpack into a directory `foo-1.0') still applies.
Send a mail to archive@cis.ohio-state.edu containing your ELAE, with the program attached.

Updating your entry

archive@cis.ohio-state.edu