Mercurial > emacs
annotate lispref/tips.texi @ 18725:07145cb40453
(sys_shutdown): New function.
author | Geoff Voelker <voelker@cs.washington.edu> |
---|---|
date | Thu, 10 Jul 1997 20:10:09 +0000 |
parents | 96762d1abb7c |
children | 8546df4cb304 |
rev | line source |
---|---|
6552 | 1 @c -*-texinfo-*- |
2 @c This is part of the GNU Emacs Lisp Reference Manual. | |
3 @c Copyright (C) 1990, 1991, 1992, 1993 Free Software Foundation, Inc. | |
4 @c See the file elisp.texi for copying conditions. | |
5 @setfilename ../info/tips | |
6 @node Tips, GNU Emacs Internals, Calendar, Top | |
17280
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
7 @appendix Tips and Conventions |
6552 | 8 @cindex tips |
9 @cindex standards of coding style | |
10 @cindex coding standards | |
11 | |
17280
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
12 This chapter describes no additional features of Emacs Lisp. Instead |
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
13 it gives advice on making effective use of the features described in the |
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
14 previous chapters, and describes conventions Emacs Lisp programmers |
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
15 should follow. |
6552 | 16 |
17 @menu | |
17280
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
18 * Coding Conventions:: Conventions for clean and robust programs. |
6552 | 19 * Compilation Tips:: Making compiled code run fast. |
20 * Documentation Tips:: Writing readable documentation strings. | |
21 * Comment Tips:: Conventions for writing comments. | |
22 * Library Headers:: Standard headers for library packages. | |
23 @end menu | |
24 | |
17280
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
25 @node Coding Conventions |
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
26 @section Emacs Lisp Coding Conventions |
6552 | 27 |
17280
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
28 Here are conventions that you should follow when writing Emacs Lisp |
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
29 code intended for widespread use: |
6552 | 30 |
31 @itemize @bullet | |
32 @item | |
33 Since all global variables share the same name space, and all functions | |
34 share another name space, you should choose a short word to distinguish | |
35 your program from other Lisp programs. Then take care to begin the | |
36 names of all global variables, constants, and functions with the chosen | |
37 prefix. This helps avoid name conflicts. | |
38 | |
39 This recommendation applies even to names for traditional Lisp | |
40 primitives that are not primitives in Emacs Lisp---even to @code{cadr}. | |
41 Believe it or not, there is more than one plausible way to define | |
42 @code{cadr}. Play it safe; append your name prefix to produce a name | |
43 like @code{foo-cadr} or @code{mylib-cadr} instead. | |
44 | |
45 If you write a function that you think ought to be added to Emacs under | |
46 a certain name, such as @code{twiddle-files}, don't call it by that name | |
47 in your program. Call it @code{mylib-twiddle-files} in your program, | |
48 and send mail to @samp{bug-gnu-emacs@@prep.ai.mit.edu} suggesting we add | |
49 it to Emacs. If and when we do, we can change the name easily enough. | |
50 | |
51 If one prefix is insufficient, your package may use two or three | |
52 alternative common prefixes, so long as they make sense. | |
53 | |
54 Separate the prefix from the rest of the symbol name with a hyphen, | |
55 @samp{-}. This will be consistent with Emacs itself and with most Emacs | |
56 Lisp programs. | |
57 | |
58 @item | |
59 It is often useful to put a call to @code{provide} in each separate | |
60 library program, at least if there is more than one entry point to the | |
61 program. | |
62 | |
63 @item | |
12098 | 64 If a file requires certain other library programs to be loaded |
65 beforehand, then the comments at the beginning of the file should say | |
66 so. Also, use @code{require} to make sure they are loaded. | |
67 | |
68 @item | |
6552 | 69 If one file @var{foo} uses a macro defined in another file @var{bar}, |
12098 | 70 @var{foo} should contain this expression before the first use of the |
71 macro: | |
72 | |
73 @example | |
74 (eval-when-compile (require '@var{bar})) | |
75 @end example | |
76 | |
77 @noindent | |
78 (And @var{bar} should contain @code{(provide '@var{bar})}, to make the | |
79 @code{require} work.) This will cause @var{bar} to be loaded when you | |
80 byte-compile @var{foo}. Otherwise, you risk compiling @var{foo} without | |
81 the necessary macro loaded, and that would produce compiled code that | |
82 won't work right. @xref{Compiling Macros}. | |
83 | |
84 Using @code{eval-when-compile} avoids loading @var{bar} when | |
85 the compiled version of @var{foo} is @emph{used}. | |
6552 | 86 |
87 @item | |
17280
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
88 When defining a major mode, please follow the major mode |
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
89 conventions. @xref{Major Mode Conventions}. |
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
90 |
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
91 @item |
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
92 When defining a minor mode, please follow the minor mode |
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
93 conventions. @xref{Minor Mode Conventions}. |
6552 | 94 |
95 @item | |
9807
d5fa87d62d62
Add function and variable name conventions.
Richard M. Stallman <rms@gnu.org>
parents:
9393
diff
changeset
|
96 If the purpose of a function is to tell you whether a certain condition |
d5fa87d62d62
Add function and variable name conventions.
Richard M. Stallman <rms@gnu.org>
parents:
9393
diff
changeset
|
97 is true or false, give the function a name that ends in @samp{p}. If |
d5fa87d62d62
Add function and variable name conventions.
Richard M. Stallman <rms@gnu.org>
parents:
9393
diff
changeset
|
98 the name is one word, add just @samp{p}; if the name is multiple words, |
d5fa87d62d62
Add function and variable name conventions.
Richard M. Stallman <rms@gnu.org>
parents:
9393
diff
changeset
|
99 add @samp{-p}. Examples are @code{framep} and @code{frame-live-p}. |
d5fa87d62d62
Add function and variable name conventions.
Richard M. Stallman <rms@gnu.org>
parents:
9393
diff
changeset
|
100 |
d5fa87d62d62
Add function and variable name conventions.
Richard M. Stallman <rms@gnu.org>
parents:
9393
diff
changeset
|
101 @item |
d5fa87d62d62
Add function and variable name conventions.
Richard M. Stallman <rms@gnu.org>
parents:
9393
diff
changeset
|
102 If a user option variable records a true-or-false condition, give it a |
d5fa87d62d62
Add function and variable name conventions.
Richard M. Stallman <rms@gnu.org>
parents:
9393
diff
changeset
|
103 name that ends in @samp{-flag}. |
d5fa87d62d62
Add function and variable name conventions.
Richard M. Stallman <rms@gnu.org>
parents:
9393
diff
changeset
|
104 |
d5fa87d62d62
Add function and variable name conventions.
Richard M. Stallman <rms@gnu.org>
parents:
9393
diff
changeset
|
105 @item |
6552 | 106 Please do not define @kbd{C-c @var{letter}} as a key in your major |
107 modes. These sequences are reserved for users; they are the | |
108 @strong{only} sequences reserved for users, so we cannot do without | |
109 them. | |
110 | |
14394
289506921917
Clarify key sequence usage conventions.
Richard M. Stallman <rms@gnu.org>
parents:
14028
diff
changeset
|
111 Instead, define sequences consisting of @kbd{C-c} followed by a control |
289506921917
Clarify key sequence usage conventions.
Richard M. Stallman <rms@gnu.org>
parents:
14028
diff
changeset
|
112 character, a digit, or certain punctuation characters. These sequences |
289506921917
Clarify key sequence usage conventions.
Richard M. Stallman <rms@gnu.org>
parents:
14028
diff
changeset
|
113 are reserved for major modes. |
6552 | 114 |
115 Changing all the major modes in Emacs 18 so they would follow this | |
11648
e09e51d7c35a
Describe uses of C-c followed by punctuation chars.
Richard M. Stallman <rms@gnu.org>
parents:
10229
diff
changeset
|
116 convention was a lot of work. Abandoning this convention would make |
e09e51d7c35a
Describe uses of C-c followed by punctuation chars.
Richard M. Stallman <rms@gnu.org>
parents:
10229
diff
changeset
|
117 that work go to waste, and inconvenience users. |
e09e51d7c35a
Describe uses of C-c followed by punctuation chars.
Richard M. Stallman <rms@gnu.org>
parents:
10229
diff
changeset
|
118 |
e09e51d7c35a
Describe uses of C-c followed by punctuation chars.
Richard M. Stallman <rms@gnu.org>
parents:
10229
diff
changeset
|
119 @item |
e09e51d7c35a
Describe uses of C-c followed by punctuation chars.
Richard M. Stallman <rms@gnu.org>
parents:
10229
diff
changeset
|
120 Sequences consisting of @kbd{C-c} followed by @kbd{@{}, @kbd{@}}, |
e09e51d7c35a
Describe uses of C-c followed by punctuation chars.
Richard M. Stallman <rms@gnu.org>
parents:
10229
diff
changeset
|
121 @kbd{<}, @kbd{>}, @kbd{:} or @kbd{;} are also reserved for major modes. |
e09e51d7c35a
Describe uses of C-c followed by punctuation chars.
Richard M. Stallman <rms@gnu.org>
parents:
10229
diff
changeset
|
122 |
e09e51d7c35a
Describe uses of C-c followed by punctuation chars.
Richard M. Stallman <rms@gnu.org>
parents:
10229
diff
changeset
|
123 @item |
e09e51d7c35a
Describe uses of C-c followed by punctuation chars.
Richard M. Stallman <rms@gnu.org>
parents:
10229
diff
changeset
|
124 Sequences consisting of @kbd{C-c} followed by any other punctuation |
e09e51d7c35a
Describe uses of C-c followed by punctuation chars.
Richard M. Stallman <rms@gnu.org>
parents:
10229
diff
changeset
|
125 character are allocated for minor modes. Using them in a major mode is |
e09e51d7c35a
Describe uses of C-c followed by punctuation chars.
Richard M. Stallman <rms@gnu.org>
parents:
10229
diff
changeset
|
126 not absolutely prohibited, but if you do that, the major mode binding |
e09e51d7c35a
Describe uses of C-c followed by punctuation chars.
Richard M. Stallman <rms@gnu.org>
parents:
10229
diff
changeset
|
127 may be shadowed from time to time by minor modes. |
6552 | 128 |
129 @item | |
130 You should not bind @kbd{C-h} following any prefix character (including | |
131 @kbd{C-c}). If you don't bind @kbd{C-h}, it is automatically available | |
132 as a help character for listing the subcommands of the prefix character. | |
133 | |
134 @item | |
135 You should not bind a key sequence ending in @key{ESC} except following | |
136 another @key{ESC}. (That is, it is ok to bind a sequence ending in | |
137 @kbd{@key{ESC} @key{ESC}}.) | |
138 | |
139 The reason for this rule is that a non-prefix binding for @key{ESC} in | |
140 any context prevents recognition of escape sequences as function keys in | |
141 that context. | |
142 | |
143 @item | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
144 Applications should not bind mouse events based on button 1 with the |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
145 shift key held down. These events include @kbd{S-mouse-1}, |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
146 @kbd{M-S-mouse-1}, @kbd{C-S-mouse-1}, and so on. They are reserved for |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
147 users. |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
148 |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
149 @item |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
150 Modes should redefine @kbd{mouse-2} as a command to follow some sort of |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
151 reference in the text of a buffer, if users usually would not want to |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
152 alter the text in that buffer by hand. Modes such as Dired, Info, |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
153 Compilation, and Occur redefine it in this way. |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
154 |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
155 @item |
9393
0bec3b6bac2f
Add a tip about enabling/disabling features.
Richard M. Stallman <rms@gnu.org>
parents:
8669
diff
changeset
|
156 When a package provides a modification of ordinary Emacs behavior, it is |
0bec3b6bac2f
Add a tip about enabling/disabling features.
Richard M. Stallman <rms@gnu.org>
parents:
8669
diff
changeset
|
157 good to include a command to enable and disable the feature, Provide a |
0bec3b6bac2f
Add a tip about enabling/disabling features.
Richard M. Stallman <rms@gnu.org>
parents:
8669
diff
changeset
|
158 command named @code{@var{whatever}-mode} which turns the feature on or |
0bec3b6bac2f
Add a tip about enabling/disabling features.
Richard M. Stallman <rms@gnu.org>
parents:
8669
diff
changeset
|
159 off, and make it autoload (@pxref{Autoload}). Design the package so |
0bec3b6bac2f
Add a tip about enabling/disabling features.
Richard M. Stallman <rms@gnu.org>
parents:
8669
diff
changeset
|
160 that simply loading it has no visible effect---that should not enable |
0bec3b6bac2f
Add a tip about enabling/disabling features.
Richard M. Stallman <rms@gnu.org>
parents:
8669
diff
changeset
|
161 the feature. Users will request the feature by invoking the command. |
0bec3b6bac2f
Add a tip about enabling/disabling features.
Richard M. Stallman <rms@gnu.org>
parents:
8669
diff
changeset
|
162 |
0bec3b6bac2f
Add a tip about enabling/disabling features.
Richard M. Stallman <rms@gnu.org>
parents:
8669
diff
changeset
|
163 @item |
0bec3b6bac2f
Add a tip about enabling/disabling features.
Richard M. Stallman <rms@gnu.org>
parents:
8669
diff
changeset
|
164 It is a bad idea to define aliases for the Emacs primitives. Use the |
0bec3b6bac2f
Add a tip about enabling/disabling features.
Richard M. Stallman <rms@gnu.org>
parents:
8669
diff
changeset
|
165 standard names instead. |
6552 | 166 |
167 @item | |
17280
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
168 Redefining (or advising) an Emacs primitive is discouraged. It may do |
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
169 the right thing for a particular program, but there is no telling what |
96762d1abb7c
(Coding Conventions): Node renamed from Style Tips.
Richard M. Stallman <rms@gnu.org>
parents:
16736
diff
changeset
|
170 other programs might break as a result. |
6552 | 171 |
172 @item | |
173 If a file does replace any of the functions or library programs of | |
174 standard Emacs, prominent comments at the beginning of the file should | |
175 say which functions are replaced, and how the behavior of the | |
176 replacements differs from that of the originals. | |
177 | |
178 @item | |
179 Please keep the names of your Emacs Lisp source files to 13 characters | |
180 or less. This way, if the files are compiled, the compiled files' names | |
181 will be 14 characters or less, which is short enough to fit on all kinds | |
182 of Unix systems. | |
183 | |
184 @item | |
185 Don't use @code{next-line} or @code{previous-line} in programs; nearly | |
186 always, @code{forward-line} is more convenient as well as more | |
187 predictable and robust. @xref{Text Lines}. | |
188 | |
189 @item | |
7601
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
190 Don't call functions that set the mark, unless setting the mark is one |
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
191 of the intended features of your program. The mark is a user-level |
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
192 feature, so it is incorrect to change the mark except to supply a value |
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
193 for the user's benefit. @xref{The Mark}. |
6552 | 194 |
195 In particular, don't use these functions: | |
196 | |
197 @itemize @bullet | |
198 @item | |
199 @code{beginning-of-buffer}, @code{end-of-buffer} | |
200 @item | |
201 @code{replace-string}, @code{replace-regexp} | |
202 @end itemize | |
203 | |
204 If you just want to move point, or replace a certain string, without any | |
205 of the other features intended for interactive users, you can replace | |
206 these functions with one or two lines of simple Lisp code. | |
207 | |
208 @item | |
8669 | 209 Use lists rather than vectors, except when there is a particular reason |
210 to use a vector. Lisp has more facilities for manipulating lists than | |
211 for vectors, and working with lists is usually more convenient. | |
212 | |
213 Vectors are advantageous for tables that are substantial in size and are | |
214 accessed in random order (not searched front to back), provided there is | |
215 no need to insert or delete elements (only lists allow that). | |
216 | |
217 @item | |
6552 | 218 The recommended way to print a message in the echo area is with |
219 the @code{message} function, not @code{princ}. @xref{The Echo Area}. | |
220 | |
221 @item | |
222 When you encounter an error condition, call the function @code{error} | |
223 (or @code{signal}). The function @code{error} does not return. | |
224 @xref{Signaling Errors}. | |
225 | |
226 Do not use @code{message}, @code{throw}, @code{sleep-for}, | |
227 or @code{beep} to report errors. | |
228 | |
229 @item | |
12098 | 230 An error message should start with a capital letter but should not end |
231 with a period. | |
232 | |
233 @item | |
13893
2576d1142ed3
Explain style of "done" messages.
Richard M. Stallman <rms@gnu.org>
parents:
12098
diff
changeset
|
234 Many commands that take a long time to execute display a message that |
2576d1142ed3
Explain style of "done" messages.
Richard M. Stallman <rms@gnu.org>
parents:
12098
diff
changeset
|
235 says @samp{Operating...} when they start, and change it to |
2576d1142ed3
Explain style of "done" messages.
Richard M. Stallman <rms@gnu.org>
parents:
12098
diff
changeset
|
236 @samp{Operating...done} when they finish. Please keep the style of |
2576d1142ed3
Explain style of "done" messages.
Richard M. Stallman <rms@gnu.org>
parents:
12098
diff
changeset
|
237 these messages uniform: @emph{no} space around the ellipsis, and |
2576d1142ed3
Explain style of "done" messages.
Richard M. Stallman <rms@gnu.org>
parents:
12098
diff
changeset
|
238 @emph{no} period at the end. |
2576d1142ed3
Explain style of "done" messages.
Richard M. Stallman <rms@gnu.org>
parents:
12098
diff
changeset
|
239 |
2576d1142ed3
Explain style of "done" messages.
Richard M. Stallman <rms@gnu.org>
parents:
12098
diff
changeset
|
240 @item |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
241 Try to avoid using recursive edits. Instead, do what the Rmail @kbd{e} |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
242 command does: use a new local keymap that contains one command defined |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
243 to switch back to the old local keymap. Or do what the |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
244 @code{edit-options} command does: switch to another buffer and let the |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
245 user switch back at will. @xref{Recursive Editing}. |
6552 | 246 |
247 @item | |
248 In some other systems there is a convention of choosing variable names | |
249 that begin and end with @samp{*}. We don't use that convention in Emacs | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
250 Lisp, so please don't use it in your programs. (Emacs uses such names |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
251 only for program-generated buffers.) The users will find Emacs more |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
252 coherent if all libraries use the same conventions. |
6552 | 253 |
254 @item | |
14028
e8d6c760f796
Explain eliminating compiler warnings about undefined variables.
Richard M. Stallman <rms@gnu.org>
parents:
13893
diff
changeset
|
255 Try to avoid compiler warnings about undefined free variables, by adding |
15198 | 256 @code{defvar} definitions for these variables. |
14028
e8d6c760f796
Explain eliminating compiler warnings about undefined variables.
Richard M. Stallman <rms@gnu.org>
parents:
13893
diff
changeset
|
257 |
e8d6c760f796
Explain eliminating compiler warnings about undefined variables.
Richard M. Stallman <rms@gnu.org>
parents:
13893
diff
changeset
|
258 If you bind a variable in one function, and use it or set it in another |
e8d6c760f796
Explain eliminating compiler warnings about undefined variables.
Richard M. Stallman <rms@gnu.org>
parents:
13893
diff
changeset
|
259 function, the compiler warns about the latter function unless the |
e8d6c760f796
Explain eliminating compiler warnings about undefined variables.
Richard M. Stallman <rms@gnu.org>
parents:
13893
diff
changeset
|
260 variable has a definition. But often these variables have short names, |
e8d6c760f796
Explain eliminating compiler warnings about undefined variables.
Richard M. Stallman <rms@gnu.org>
parents:
13893
diff
changeset
|
261 and it is not clean for Lisp packages to define such variables names. |
e8d6c760f796
Explain eliminating compiler warnings about undefined variables.
Richard M. Stallman <rms@gnu.org>
parents:
13893
diff
changeset
|
262 Therefore, you should rename the variable to start with the name prefix |
e8d6c760f796
Explain eliminating compiler warnings about undefined variables.
Richard M. Stallman <rms@gnu.org>
parents:
13893
diff
changeset
|
263 used for the other functions and variables in your package. |
e8d6c760f796
Explain eliminating compiler warnings about undefined variables.
Richard M. Stallman <rms@gnu.org>
parents:
13893
diff
changeset
|
264 |
e8d6c760f796
Explain eliminating compiler warnings about undefined variables.
Richard M. Stallman <rms@gnu.org>
parents:
13893
diff
changeset
|
265 @item |
6552 | 266 Indent each function with @kbd{C-M-q} (@code{indent-sexp}) using the |
267 default indentation parameters. | |
268 | |
269 @item | |
270 Don't make a habit of putting close-parentheses on lines by themselves; | |
271 Lisp programmers find this disconcerting. Once in a while, when there | |
272 is a sequence of many consecutive close-parentheses, it may make sense | |
273 to split them in one or two significant places. | |
274 | |
275 @item | |
276 Please put a copyright notice on the file if you give copies to anyone. | |
277 Use the same lines that appear at the top of the Lisp files in Emacs | |
278 itself. If you have not signed papers to assign the copyright to the | |
279 Foundation, then place your name in the copyright notice in place of the | |
280 Foundation's name. | |
281 @end itemize | |
282 | |
283 @node Compilation Tips | |
284 @section Tips for Making Compiled Code Fast | |
285 @cindex execution speed | |
286 @cindex speedups | |
287 | |
288 Here are ways of improving the execution speed of byte-compiled | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
289 Lisp programs. |
6552 | 290 |
291 @itemize @bullet | |
292 @item | |
293 @cindex profiling | |
294 @cindex timing programs | |
295 @cindex @file{profile.el} | |
296 Use the @file{profile} library to profile your program. See the file | |
297 @file{profile.el} for instructions. | |
298 | |
299 @item | |
300 Use iteration rather than recursion whenever possible. | |
301 Function calls are slow in Emacs Lisp even when a compiled function | |
302 is calling another compiled function. | |
303 | |
304 @item | |
12098 | 305 Using the primitive list-searching functions @code{memq}, @code{member}, |
306 @code{assq}, or @code{assoc} is even faster than explicit iteration. It | |
307 may be worth rearranging a data structure so that one of these primitive | |
308 search functions can be used. | |
6552 | 309 |
310 @item | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
311 Certain built-in functions are handled specially in byte-compiled code, |
6552 | 312 avoiding the need for an ordinary function call. It is a good idea to |
313 use these functions rather than alternatives. To see whether a function | |
314 is handled specially by the compiler, examine its @code{byte-compile} | |
315 property. If the property is non-@code{nil}, then the function is | |
316 handled specially. | |
317 | |
318 For example, the following input will show you that @code{aref} is | |
319 compiled specially (@pxref{Array Functions}) while @code{elt} is not | |
320 (@pxref{Sequence Functions}): | |
321 | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
322 @example |
6552 | 323 @group |
324 (get 'aref 'byte-compile) | |
325 @result{} byte-compile-two-args | |
326 @end group | |
327 | |
328 @group | |
329 (get 'elt 'byte-compile) | |
330 @result{} nil | |
331 @end group | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
332 @end example |
6552 | 333 |
334 @item | |
335 If calling a small function accounts for a substantial part of your | |
336 program's running time, make the function inline. This eliminates | |
337 the function call overhead. Since making a function inline reduces | |
338 the flexibility of changing the program, don't do it unless it gives | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
339 a noticeable speedup in something slow enough that users care about |
6552 | 340 the speed. @xref{Inline Functions}. |
341 @end itemize | |
342 | |
343 @node Documentation Tips | |
344 @section Tips for Documentation Strings | |
345 | |
346 Here are some tips for the writing of documentation strings. | |
347 | |
348 @itemize @bullet | |
349 @item | |
7601
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
350 Every command, function, or variable intended for users to know about |
6552 | 351 should have a documentation string. |
352 | |
353 @item | |
10225
2e5dcd5f3090
Recommend doc strings for all functions and variables.
Richard M. Stallman <rms@gnu.org>
parents:
9807
diff
changeset
|
354 An internal variable or subroutine of a Lisp program might as well have |
2e5dcd5f3090
Recommend doc strings for all functions and variables.
Richard M. Stallman <rms@gnu.org>
parents:
9807
diff
changeset
|
355 a documentation string. In earlier Emacs versions, you could save space |
2e5dcd5f3090
Recommend doc strings for all functions and variables.
Richard M. Stallman <rms@gnu.org>
parents:
9807
diff
changeset
|
356 by using a comment instead of a documentation string, but that is no |
2e5dcd5f3090
Recommend doc strings for all functions and variables.
Richard M. Stallman <rms@gnu.org>
parents:
9807
diff
changeset
|
357 longer the case. |
6552 | 358 |
359 @item | |
360 The first line of the documentation string should consist of one or two | |
7601
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
361 complete sentences that stand on their own as a summary. @kbd{M-x |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
362 apropos} displays just the first line, and if it doesn't stand on its |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
363 own, the result looks bad. In particular, start the first line with a |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
364 capital letter and end with a period. |
6552 | 365 |
7601
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
366 The documentation string can have additional lines that expand on the |
6552 | 367 details of how to use the function or variable. The additional lines |
368 should be made up of complete sentences also, but they may be filled if | |
369 that looks good. | |
370 | |
371 @item | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
372 For consistency, phrase the verb in the first sentence of a |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
373 documentation string as an infinitive with ``to'' omitted. For |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
374 instance, use ``Return the cons of A and B.'' in preference to ``Returns |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
375 the cons of A and B@.'' Usually it looks good to do likewise for the |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
376 rest of the first paragraph. Subsequent paragraphs usually look better |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
377 if they have proper subjects. |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
378 |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
379 @item |
6552 | 380 Write documentation strings in the active voice, not the passive, and in |
381 the present tense, not the future. For instance, use ``Return a list | |
382 containing A and B.'' instead of ``A list containing A and B will be | |
383 returned.'' | |
384 | |
385 @item | |
386 Avoid using the word ``cause'' (or its equivalents) unnecessarily. | |
387 Instead of, ``Cause Emacs to display text in boldface,'' write just | |
388 ``Display text in boldface.'' | |
389 | |
390 @item | |
391 Do not start or end a documentation string with whitespace. | |
392 | |
393 @item | |
394 Format the documentation string so that it fits in an Emacs window on an | |
7601
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
395 80-column screen. It is a good idea for most lines to be no wider than |
6552 | 396 60 characters. The first line can be wider if necessary to fit the |
397 information that ought to be there. | |
398 | |
399 However, rather than simply filling the entire documentation string, you | |
400 can make it much more readable by choosing line breaks with care. | |
401 Use blank lines between topics if the documentation string is long. | |
402 | |
403 @item | |
404 @strong{Do not} indent subsequent lines of a documentation string so | |
405 that the text is lined up in the source code with the text of the first | |
406 line. This looks nice in the source code, but looks bizarre when users | |
407 view the documentation. Remember that the indentation before the | |
408 starting double-quote is not part of the string! | |
409 | |
410 @item | |
16671
9fa09185bca0
Explain how disabled commands' doc strings are displayed.
Richard M. Stallman <rms@gnu.org>
parents:
15198
diff
changeset
|
411 When the user tries to use a disabled command, Emacs displays just the |
9fa09185bca0
Explain how disabled commands' doc strings are displayed.
Richard M. Stallman <rms@gnu.org>
parents:
15198
diff
changeset
|
412 first paragraph of its documentation string---everything through the |
9fa09185bca0
Explain how disabled commands' doc strings are displayed.
Richard M. Stallman <rms@gnu.org>
parents:
15198
diff
changeset
|
413 first blank line. If you wish, you can choose which information to |
9fa09185bca0
Explain how disabled commands' doc strings are displayed.
Richard M. Stallman <rms@gnu.org>
parents:
15198
diff
changeset
|
414 include before the first blank line so as to make this display useful. |
9fa09185bca0
Explain how disabled commands' doc strings are displayed.
Richard M. Stallman <rms@gnu.org>
parents:
15198
diff
changeset
|
415 |
9fa09185bca0
Explain how disabled commands' doc strings are displayed.
Richard M. Stallman <rms@gnu.org>
parents:
15198
diff
changeset
|
416 @item |
6552 | 417 A variable's documentation string should start with @samp{*} if the |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
418 variable is one that users would often want to set interactively. If |
7601
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
419 the value is a long list, or a function, or if the variable would be set |
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
420 only in init files, then don't start the documentation string with |
6552 | 421 @samp{*}. @xref{Defining Variables}. |
422 | |
423 @item | |
424 The documentation string for a variable that is a yes-or-no flag should | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
425 start with words such as ``Non-nil means@dots{}'', to make it clear that |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
426 all non-@code{nil} values are equivalent and indicate explicitly what |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
427 @code{nil} and non-@code{nil} mean. |
6552 | 428 |
429 @item | |
430 When a function's documentation string mentions the value of an argument | |
431 of the function, use the argument name in capital letters as if it were | |
432 a name for that value. Thus, the documentation string of the function | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
433 @code{/} refers to its second argument as @samp{DIVISOR}, because the |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
434 actual argument name is @code{divisor}. |
6552 | 435 |
436 Also use all caps for meta-syntactic variables, such as when you show | |
437 the decomposition of a list or vector into subunits, some of which may | |
438 vary. | |
439 | |
440 @item | |
441 @iftex | |
442 When a documentation string refers to a Lisp symbol, write it as it | |
443 would be printed (which usually means in lower case), with single-quotes | |
444 around it. For example: @samp{`lambda'}. There are two exceptions: | |
445 write @code{t} and @code{nil} without single-quotes. | |
446 @end iftex | |
447 @ifinfo | |
448 When a documentation string refers to a Lisp symbol, write it as it | |
449 would be printed (which usually means in lower case), with single-quotes | |
450 around it. For example: @samp{lambda}. There are two exceptions: write | |
451 t and nil without single-quotes. (In this manual, we normally do use | |
452 single-quotes for those symbols.) | |
453 @end ifinfo | |
454 | |
455 @item | |
456 Don't write key sequences directly in documentation strings. Instead, | |
457 use the @samp{\\[@dots{}]} construct to stand for them. For example, | |
16736
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
16671
diff
changeset
|
458 instead of writing @samp{C-f}, write the construct |
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
16671
diff
changeset
|
459 @samp{\\[forward-char]}. When Emacs displays the documentation string, |
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
16671
diff
changeset
|
460 it substitutes whatever key is currently bound to @code{forward-char}. |
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
16671
diff
changeset
|
461 (This is normally @samp{C-f}, but it may be some other character if the |
981e116b4ac6
Minor cleanups for overfull hboxes.
Richard M. Stallman <rms@gnu.org>
parents:
16671
diff
changeset
|
462 user has moved key bindings.) @xref{Keys in Documentation}. |
6552 | 463 |
464 @item | |
465 In documentation strings for a major mode, you will want to refer to the | |
466 key bindings of that mode's local map, rather than global ones. | |
467 Therefore, use the construct @samp{\\<@dots{}>} once in the | |
468 documentation string to specify which key map to use. Do this before | |
469 the first use of @samp{\\[@dots{}]}. The text inside the | |
470 @samp{\\<@dots{}>} should be the name of the variable containing the | |
471 local keymap for the major mode. | |
472 | |
473 It is not practical to use @samp{\\[@dots{}]} very many times, because | |
474 display of the documentation string will become slow. So use this to | |
475 describe the most important commands in your major mode, and then use | |
476 @samp{\\@{@dots{}@}} to display the rest of the mode's keymap. | |
477 @end itemize | |
478 | |
479 @node Comment Tips | |
480 @section Tips on Writing Comments | |
481 | |
482 We recommend these conventions for where to put comments and how to | |
483 indent them: | |
484 | |
485 @table @samp | |
486 @item ; | |
487 Comments that start with a single semicolon, @samp{;}, should all be | |
488 aligned to the same column on the right of the source code. Such | |
489 comments usually explain how the code on the same line does its job. In | |
490 Lisp mode and related modes, the @kbd{M-;} (@code{indent-for-comment}) | |
491 command automatically inserts such a @samp{;} in the right place, or | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
492 aligns such a comment if it is already present. |
6552 | 493 |
7601
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
494 This and following examples are taken from the Emacs sources. |
6552 | 495 |
496 @smallexample | |
497 @group | |
498 (setq base-version-list ; there was a base | |
499 (assoc (substring fn 0 start-vn) ; version to which | |
500 file-version-assoc-list)) ; this looks like | |
501 ; a subversion | |
502 @end group | |
503 @end smallexample | |
504 | |
505 @item ;; | |
506 Comments that start with two semicolons, @samp{;;}, should be aligned to | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
507 the same level of indentation as the code. Such comments usually |
6552 | 508 describe the purpose of the following lines or the state of the program |
509 at that point. For example: | |
510 | |
511 @smallexample | |
512 @group | |
513 (prog1 (setq auto-fill-function | |
514 @dots{} | |
515 @dots{} | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
516 ;; update mode line |
6552 | 517 (force-mode-line-update))) |
518 @end group | |
519 @end smallexample | |
520 | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
521 Every function that has no documentation string (because it is use only |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
522 internally within the package it belongs to), should have instead a |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
523 two-semicolon comment right before the function, explaining what the |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
524 function does and how to call it properly. Explain precisely what each |
7601
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
525 argument means and how the function interprets its possible values. |
6552 | 526 |
527 @item ;;; | |
528 Comments that start with three semicolons, @samp{;;;}, should start at | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
529 the left margin. Such comments are used outside function definitions to |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
530 make general statements explaining the design principles of the program. |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
531 For example: |
6552 | 532 |
533 @smallexample | |
534 @group | |
535 ;;; This Lisp code is run in Emacs | |
536 ;;; when it is to operate as a server | |
537 ;;; for other processes. | |
538 @end group | |
539 @end smallexample | |
540 | |
7601
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
541 Another use for triple-semicolon comments is for commenting out lines |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
542 within a function. We use triple-semicolons for this precisely so that |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
543 they remain at the left margin. |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
544 |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
545 @smallexample |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
546 (defun foo (a) |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
547 ;;; This is no longer necessary. |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
548 ;;; (force-mode-line-update) |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
549 (message "Finished with %s" a)) |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
550 @end smallexample |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
551 |
6552 | 552 @item ;;;; |
553 Comments that start with four semicolons, @samp{;;;;}, should be aligned | |
554 to the left margin and are used for headings of major sections of a | |
555 program. For example: | |
556 | |
557 @smallexample | |
558 ;;;; The kill ring | |
559 @end smallexample | |
560 @end table | |
561 | |
562 @noindent | |
563 The indentation commands of the Lisp modes in Emacs, such as @kbd{M-;} | |
564 (@code{indent-for-comment}) and @key{TAB} (@code{lisp-indent-line}) | |
565 automatically indent comments according to these conventions, | |
7601
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
566 depending on the number of semicolons. @xref{Comments,, |
6552 | 567 Manipulating Comments, emacs, The GNU Emacs Manual}. |
568 | |
569 @node Library Headers | |
570 @section Conventional Headers for Emacs Libraries | |
571 @cindex header comments | |
572 @cindex library header comments | |
573 | |
574 Emacs 19 has conventions for using special comments in Lisp libraries | |
575 to divide them into sections and give information such as who wrote | |
576 them. This section explains these conventions. First, an example: | |
577 | |
578 @smallexample | |
579 @group | |
580 ;;; lisp-mnt.el --- minor mode for Emacs Lisp maintainers | |
581 | |
582 ;; Copyright (C) 1992 Free Software Foundation, Inc. | |
583 @end group | |
584 | |
585 ;; Author: Eric S. Raymond <esr@@snark.thyrsus.com> | |
586 ;; Maintainer: Eric S. Raymond <esr@@snark.thyrsus.com> | |
587 ;; Created: 14 Jul 1992 | |
588 ;; Version: 1.2 | |
589 @group | |
590 ;; Keywords: docs | |
591 | |
592 ;; This file is part of GNU Emacs. | |
7601
c5927c75b2b5
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6959
diff
changeset
|
593 @var{copying permissions}@dots{} |
6552 | 594 @end group |
595 @end smallexample | |
596 | |
597 The very first line should have this format: | |
598 | |
599 @example | |
600 ;;; @var{filename} --- @var{description} | |
601 @end example | |
602 | |
603 @noindent | |
604 The description should be complete in one line. | |
605 | |
606 After the copyright notice come several @dfn{header comment} lines, | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
607 each beginning with @samp{;; @var{header-name}:}. Here is a table of |
6552 | 608 the conventional possibilities for @var{header-name}: |
609 | |
610 @table @samp | |
611 @item Author | |
612 This line states the name and net address of at least the principal | |
613 author of the library. | |
614 | |
615 If there are multiple authors, you can list them on continuation lines | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
616 led by @code{;;} and a tab character, like this: |
6552 | 617 |
618 @smallexample | |
619 @group | |
620 ;; Author: Ashwin Ram <Ram-Ashwin@@cs.yale.edu> | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
621 ;; Dave Sill <de5@@ornl.gov> |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
622 ;; Dave Brennan <brennan@@hal.com> |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
623 ;; Eric Raymond <esr@@snark.thyrsus.com> |
6552 | 624 @end group |
625 @end smallexample | |
626 | |
627 @item Maintainer | |
628 This line should contain a single name/address as in the Author line, or | |
6959
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
629 an address only, or the string @samp{FSF}. If there is no maintainer |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
630 line, the person(s) in the Author field are presumed to be the |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
631 maintainers. The example above is mildly bogus because the maintainer |
3b19456b877a
*** empty log message ***
Richard M. Stallman <rms@gnu.org>
parents:
6552
diff
changeset
|
632 line is redundant. |
6552 | 633 |
634 The idea behind the @samp{Author} and @samp{Maintainer} lines is to make | |
635 possible a Lisp function to ``send mail to the maintainer'' without | |
636 having to mine the name out by hand. | |
637 | |
638 Be sure to surround the network address with @samp{<@dots{}>} if | |
639 you include the person's full name as well as the network address. | |
640 | |
641 @item Created | |
642 This optional line gives the original creation date of the | |
643 file. For historical interest only. | |
644 | |
645 @item Version | |
646 If you wish to record version numbers for the individual Lisp program, put | |
647 them in this line. | |
648 | |
649 @item Adapted-By | |
650 In this header line, place the name of the person who adapted the | |
651 library for installation (to make it fit the style conventions, for | |
652 example). | |
653 | |
654 @item Keywords | |
655 This line lists keywords for the @code{finder-by-keyword} help command. | |
656 This field is important; it's how people will find your package when | |
10229
634f36d4b2ae
Give syntax of keywords.
Richard M. Stallman <rms@gnu.org>
parents:
10225
diff
changeset
|
657 they're looking for things by topic area. To separate the keywords, you |
634f36d4b2ae
Give syntax of keywords.
Richard M. Stallman <rms@gnu.org>
parents:
10225
diff
changeset
|
658 can use spaces, commas, or both. |
6552 | 659 @end table |
660 | |
661 Just about every Lisp library ought to have the @samp{Author} and | |
662 @samp{Keywords} header comment lines. Use the others if they are | |
663 appropriate. You can also put in header lines with other header | |
664 names---they have no standard meanings, so they can't do any harm. | |
665 | |
666 We use additional stylized comments to subdivide the contents of the | |
667 library file. Here is a table of them: | |
668 | |
669 @table @samp | |
670 @item ;;; Commentary: | |
671 This begins introductory comments that explain how the library works. | |
672 It should come right after the copying permissions. | |
673 | |
674 @item ;;; Change log: | |
675 This begins change log information stored in the library file (if you | |
676 store the change history there). For most of the Lisp | |
677 files distributed with Emacs, the change history is kept in the file | |
678 @file{ChangeLog} and not in the source file at all; these files do | |
679 not have a @samp{;;; Change log:} line. | |
680 | |
681 @item ;;; Code: | |
682 This begins the actual code of the program. | |
683 | |
684 @item ;;; @var{filename} ends here | |
685 This is the @dfn{footer line}; it appears at the very end of the file. | |
686 Its purpose is to enable people to detect truncated versions of the file | |
687 from the lack of a footer line. | |
688 @end table |