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