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