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