Go to the previous, next section.

Tips and Standards

This chapter describes no additional features of Emacs Lisp. Instead it gives advice on making effective use of the features described in the previous chapters.

Writing Clean Lisp Programs

Here are some tips for avoiding common errors in writing Lisp code intended for widespread use:

Tips for Making Compiled Code Fast

Here are ways of improving the execution speed of byte-compiled lisp programs.

Tips for Documentation Strings

Here are some tips for the writing of documentation strings.

Tips on Writing Comments

We recommend these conventions for where to put comments and how to indent them:

Comments that start with a single semicolon, `;', should all be aligned to the same column on the right of the source code. Such comments usually explain how the code on the same line does its job. In Lisp mode and related modes, the M-; (indent-for-comment) command automatically inserts such a `;' in the right place, or aligns such a comment if it is already inserted.

(The following examples are taken from the Emacs sources.)

(setq base-version-list                 ; there was a base
      (assoc (substring fn 0 start-vn)  ; version to which
             file-version-assoc-list))  ; this looks like
                                        ; a subversion

Comments that start with two semicolons, `;;', should be aligned to the same level of indentation as the code. Such comments are used to describe the purpose of the following lines or the state of the program at that point. For example:

(prog1 (setq auto-fill-function
  ;; update mode-line

These comments are also written before a function definition to explain what the function does and how to call it properly.

Comments that start with three semicolons, `;;;', should start at the left margin. Such comments are not used within function definitions, but are used to make more general comments. For example:

;;; This Lisp code is run in Emacs
;;; when it is to operate as a server
;;; for other processes.

Comments that start with four semicolons, `;;;;', should be aligned to the left margin and are used for headings of major sections of a program. For example:

;;;; The kill ring

The indentation commands of the Lisp modes in Emacs, such as M-; (indent-for-comment) and TAB (lisp-indent-line) automatically indent comments according to these conventions, depending on the the number of semicolons. See section `Manipulating Comments' in The GNU Emacs Manual.

If you wish to "comment out" a number of lines of code, use triple semicolons at the beginnings of the lines.

Any character may be included in a comment, but it is advisable to precede a character with syntactic significance in Lisp (such as `\' or unpaired `(' or `)') with a `\', to prevent it from confusing the Emacs commands for editing Lisp.

Conventional Headers for Emacs Libraries

Emacs 19 has conventions for using special comments in Lisp libraries to divide them into sections and give information such as who wrote them. This section explains these conventions. First, an example:

;;; lisp-mnt.el -- minor mode for Emacs Lisp maintainers

;; Copyright (C) 1992 Free Software Foundation, Inc.

;; Author: Eric S. Raymond <esr@snark.thyrsus.com>
;; Maintainer: Eric S. Raymond <esr@snark.thyrsus.com>
;; Created: 14 Jul 1992
;; Version: 1.2
;; Keywords: docs

;; This file is part of GNU Emacs.
copying conditions...

The very first line should have this format:

;;; filename -- description

The description should be complete in one line.

After the copyright notice come several header comment lines, each beginning with `;;; header-name:'. Here is a table of the conventional possibilities for header-name:

This line states the name and net address of at least the principal author of the library.

If there are multiple authors, you can list them on continuation lines led by ;;<TAB>, like this:

;; Author: Ashwin Ram <Ram-Ashwin@cs.yale.edu>
;;	Dave Sill <de5@ornl.gov>
;;	Dave Brennan <brennan@hal.com>
;;	Eric Raymond <esr@snark.thyrsus.com>

This line should contain a single name/address as in the Author line, or an address only, or the string "FSF". If there is no maintainer line, the person(s) in the Author field are presumed to be the maintainers. The example above is mildly bogus because the maintainer line is redundant.

The idea behind the `Author' and `Maintainer' lines is to make possible a Lisp function to "send mail to the maintainer" without having to mine the name out by hand.

Be sure to surround the network address with `<...>' if you include the person's full name as well as the network address.

This optional line gives the original creation date of the file. For historical interest only.

If you wish to record version numbers for the individual Lisp program, put them in this line.

In this header line, place the name of the person who adapted the library for installation (to make it fit the style conventions, for example).

This line lists keywords for the finder-by-keyword help command. This field is important; it's how people will find your package when they're looking for things by topic area.

Just about every Lisp library ought to have the `Author' and `Keywords' header comment lines. Use the others if they are appropriate. You can also put in header lines with other header names--they have no standard meanings, so they can't do any harm.

We use additional stylized comments to subdivide the contents of the library file. Here is a table of them:

`;;; Commentary:'
This begins introductory comments that explain how the library works. It should come right after the copying permissions.

`;;; Change log:'
This begins change log information stored in the library file (if you store the change history there). For most of the Lisp files distributed with Emacs, the change history is kept in the file `ChangeLog' and not in the source file at all; these files do not have a `;;; Change log:' line.

`;;; Code:'
This begins the actual code of the program.

`;;; filename ends here'
This is the footer line; it appears at the very end of the file. Its purpose is to enable people to detect truncated versions of the file from the lack of a footer line.

Go to the previous, next section.