Commit | Line | Data |
---|---|---|
83ac6b45 RS |
1 | @c -*-texinfo-*- |
2 | @c This is part of the GNU Emacs Lisp Reference Manual. | |
651f374c TTN |
3 | @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 2002, 2003, 2004, |
4 | @c 2005 Free Software Foundation, Inc. | |
83ac6b45 RS |
5 | @c See the file elisp.texi for copying conditions. |
6 | @setfilename ../info/intro | |
7 | ||
e4a29e5a | 8 | @node Introduction, Lisp Data Types, Top, Top |
83ac6b45 | 9 | @comment node-name, next, previous, up |
83ac6b45 RS |
10 | @chapter Introduction |
11 | ||
12 | Most of the GNU Emacs text editor is written in the programming | |
13 | language called Emacs Lisp. You can write new code in Emacs Lisp and | |
14 | install it as an extension to the editor. However, Emacs Lisp is more | |
15 | than a mere ``extension language''; it is a full computer programming | |
16 | language in its own right. You can use it as you would any other | |
17 | programming language. | |
18 | ||
19 | Because Emacs Lisp is designed for use in an editor, it has special | |
20 | features for scanning and parsing text as well as features for handling | |
21 | files, buffers, displays, subprocesses, and so on. Emacs Lisp is | |
22 | closely integrated with the editing facilities; thus, editing commands | |
23 | are functions that can also conveniently be called from Lisp programs, | |
24 | and parameters for customization are ordinary Lisp variables. | |
25 | ||
a9f0a989 RS |
26 | This manual attempts to be a full description of Emacs Lisp. For a |
27 | beginner's introduction to Emacs Lisp, see @cite{An Introduction to | |
28 | Emacs Lisp Programming}, by Bob Chassell, also published by the Free | |
29 | Software Foundation. This manual presumes considerable familiarity with | |
30 | the use of Emacs for editing; see @cite{The GNU Emacs Manual} for this | |
31 | basic information. | |
32 | ||
33 | Generally speaking, the earlier chapters describe features of Emacs | |
34 | Lisp that have counterparts in many programming languages, and later | |
35 | chapters describe features that are peculiar to Emacs Lisp or relate | |
36 | specifically to editing. | |
83ac6b45 | 37 | |
4435c8d4 LK |
38 | This is edition @value{VERSION} of the GNU Emacs Lisp Reference |
39 | Manual, corresponding to Emacs version @value{EMACSVER}. | |
83ac6b45 RS |
40 | |
41 | @menu | |
42 | * Caveats:: Flaws and a request for help. | |
43 | * Lisp History:: Emacs Lisp is descended from Maclisp. | |
44 | * Conventions:: How the manual is formatted. | |
a9f0a989 | 45 | * Version Info:: Which Emacs version is running? |
83ac6b45 RS |
46 | * Acknowledgements:: The authors, editors, and sponsors of this manual. |
47 | @end menu | |
48 | ||
49 | @node Caveats | |
50 | @section Caveats | |
30db19b9 | 51 | @cindex bugs in this manual |
83ac6b45 RS |
52 | |
53 | This manual has gone through numerous drafts. It is nearly complete | |
7791402e RS |
54 | but not flawless. There are a few topics that are not covered, either |
55 | because we consider them secondary (such as most of the individual | |
56 | modes) or because they are yet to be written. Because we are not able | |
57 | to deal with them completely, we have left out several parts | |
58 | intentionally. This includes most information about usage on VMS. | |
83ac6b45 RS |
59 | |
60 | The manual should be fully correct in what it does cover, and it is | |
61 | therefore open to criticism on anything it says---from specific examples | |
62 | and descriptive text, to the ordering of chapters and sections. If | |
63 | something is confusing, or you find that you have to look at the sources | |
64 | or experiment to learn something not covered in the manual, then perhaps | |
65 | the manual should be fixed. Please let us know. | |
66 | ||
67 | @iftex | |
a40d4712 PR |
68 | As you use this manual, we ask that you mark pages with corrections so |
69 | you can later look them up and send them to us. If you think of a simple, | |
7791402e | 70 | real-life example for a function or group of functions, please make an |
83ac6b45 RS |
71 | effort to write it up and send it in. Please reference any comments to |
72 | the chapter name, section name, and function name, as appropriate, since | |
7791402e RS |
73 | page numbers and chapter and section numbers will change and we may have |
74 | trouble finding the text you are talking about. Also state the number | |
75 | of the edition you are criticizing. | |
83ac6b45 | 76 | @end iftex |
37680279 | 77 | @ifnottex |
83ac6b45 RS |
78 | |
79 | As you use this manual, we ask that you send corrections as soon as you | |
80 | find them. If you think of a simple, real life example for a function | |
81 | or group of functions, please make an effort to write it up and send it | |
82 | in. Please reference any comments to the node name and function or | |
83 | variable name, as appropriate. Also state the number of the edition | |
a40d4712 | 84 | you are criticizing. |
37680279 | 85 | @end ifnottex |
83ac6b45 | 86 | |
5a6f4c95 RS |
87 | @cindex bugs |
88 | @cindex suggestions | |
83ac6b45 RS |
89 | Please mail comments and corrections to |
90 | ||
91 | @example | |
a9f0a989 | 92 | bug-lisp-manual@@gnu.org |
83ac6b45 RS |
93 | @end example |
94 | ||
95 | @noindent | |
96 | We let mail to this list accumulate unread until someone decides to | |
97 | apply the corrections. Months, and sometimes years, go by between | |
98 | updates. So please attach no significance to the lack of a reply---your | |
99 | mail @emph{will} be acted on in due time. If you want to contact the | |
100 | Emacs maintainers more quickly, send mail to | |
a9f0a989 | 101 | @code{bug-gnu-emacs@@gnu.org}. |
83ac6b45 | 102 | |
83ac6b45 RS |
103 | @node Lisp History |
104 | @section Lisp History | |
105 | @cindex Lisp history | |
106 | ||
a9f0a989 | 107 | Lisp (LISt Processing language) was first developed in the late 1950s |
83ac6b45 | 108 | at the Massachusetts Institute of Technology for research in artificial |
a9f0a989 | 109 | intelligence. The great power of the Lisp language makes it ideal |
83ac6b45 RS |
110 | for other purposes as well, such as writing editing commands. |
111 | ||
112 | @cindex Maclisp | |
113 | @cindex Common Lisp | |
114 | Dozens of Lisp implementations have been built over the years, each | |
115 | with its own idiosyncrasies. Many of them were inspired by Maclisp, | |
a9f0a989 | 116 | which was written in the 1960s at MIT's Project MAC. Eventually the |
7791402e | 117 | implementors of the descendants of Maclisp came together and developed a |
a9f0a989 | 118 | standard for Lisp systems, called Common Lisp. In the meantime, Gerry |
969fe9b5 RS |
119 | Sussman and Guy Steele at MIT developed a simplified but very powerful |
120 | dialect of Lisp, called Scheme. | |
83ac6b45 RS |
121 | |
122 | GNU Emacs Lisp is largely inspired by Maclisp, and a little by Common | |
123 | Lisp. If you know Common Lisp, you will notice many similarities. | |
a9f0a989 | 124 | However, many features of Common Lisp have been omitted or |
83ac6b45 RS |
125 | simplified in order to reduce the memory requirements of GNU Emacs. |
126 | Sometimes the simplifications are so drastic that a Common Lisp user | |
127 | might be very confused. We will occasionally point out how GNU Emacs | |
128 | Lisp differs from Common Lisp. If you don't know Common Lisp, don't | |
129 | worry about it; this manual is self-contained. | |
130 | ||
a9f0a989 RS |
131 | @pindex cl |
132 | A certain amount of Common Lisp emulation is available via the | |
0eeca3c1 | 133 | @file{cl} library. @inforef{Top, Overview, cl}. |
a9f0a989 | 134 | |
969fe9b5 | 135 | Emacs Lisp is not at all influenced by Scheme; but the GNU project has |
a9f0a989 RS |
136 | an implementation of Scheme, called Guile. We use Guile in all new GNU |
137 | software that calls for extensibility. | |
969fe9b5 | 138 | |
83ac6b45 RS |
139 | @node Conventions |
140 | @section Conventions | |
141 | ||
142 | This section explains the notational conventions that are used in this | |
143 | manual. You may want to skip this section and refer back to it later. | |
144 | ||
145 | @menu | |
146 | * Some Terms:: Explanation of terms we use in this manual. | |
147 | * nil and t:: How the symbols @code{nil} and @code{t} are used. | |
148 | * Evaluation Notation:: The format we use for examples of evaluation. | |
a9f0a989 | 149 | * Printing Notation:: The format we use when examples print text. |
83ac6b45 RS |
150 | * Error Messages:: The format we use for examples of errors. |
151 | * Buffer Text Notation:: The format we use for buffer contents in examples. | |
152 | * Format of Descriptions:: Notation for describing functions, variables, etc. | |
153 | @end menu | |
154 | ||
155 | @node Some Terms | |
156 | @subsection Some Terms | |
157 | ||
158 | Throughout this manual, the phrases ``the Lisp reader'' and ``the Lisp | |
a9f0a989 RS |
159 | printer'' refer to those routines in Lisp that convert textual |
160 | representations of Lisp objects into actual Lisp objects, and vice | |
83ac6b45 RS |
161 | versa. @xref{Printed Representation}, for more details. You, the |
162 | person reading this manual, are thought of as ``the programmer'' and are | |
a9f0a989 RS |
163 | addressed as ``you''. ``The user'' is the person who uses Lisp |
164 | programs, including those you write. | |
83ac6b45 RS |
165 | |
166 | @cindex fonts | |
8241495d RS |
167 | Examples of Lisp code are formatted like this: @code{(list 1 2 3)}. |
168 | Names that represent metasyntactic variables, or arguments to a function | |
169 | being described, are formatted like this: @var{first-number}. | |
83ac6b45 RS |
170 | |
171 | @node nil and t | |
172 | @subsection @code{nil} and @code{t} | |
173 | @cindex @code{nil}, uses of | |
174 | @cindex truth value | |
175 | @cindex boolean | |
176 | @cindex false | |
177 | ||
bfe721d1 | 178 | In Lisp, the symbol @code{nil} has three separate meanings: it |
83ac6b45 RS |
179 | is a symbol with the name @samp{nil}; it is the logical truth value |
180 | @var{false}; and it is the empty list---the list of zero elements. | |
181 | When used as a variable, @code{nil} always has the value @code{nil}. | |
182 | ||
183 | As far as the Lisp reader is concerned, @samp{()} and @samp{nil} are | |
184 | identical: they stand for the same object, the symbol @code{nil}. The | |
185 | different ways of writing the symbol are intended entirely for human | |
186 | readers. After the Lisp reader has read either @samp{()} or @samp{nil}, | |
187 | there is no way to determine which representation was actually written | |
188 | by the programmer. | |
189 | ||
190 | In this manual, we use @code{()} when we wish to emphasize that it | |
191 | means the empty list, and we use @code{nil} when we wish to emphasize | |
192 | that it means the truth value @var{false}. That is a good convention to use | |
193 | in Lisp programs also. | |
194 | ||
195 | @example | |
196 | (cons 'foo ()) ; @r{Emphasize the empty list} | |
197 | (not nil) ; @r{Emphasize the truth value @var{false}} | |
198 | @end example | |
199 | ||
0c6087a6 | 200 | @cindex @code{t}, uses of |
83ac6b45 RS |
201 | @cindex true |
202 | In contexts where a truth value is expected, any non-@code{nil} value | |
203 | is considered to be @var{true}. However, @code{t} is the preferred way | |
204 | to represent the truth value @var{true}. When you need to choose a | |
205 | value which represents @var{true}, and there is no other basis for | |
a9f0a989 RS |
206 | choosing, use @code{t}. The symbol @code{t} always has the value |
207 | @code{t}. | |
83ac6b45 RS |
208 | |
209 | In Emacs Lisp, @code{nil} and @code{t} are special symbols that always | |
210 | evaluate to themselves. This is so that you do not need to quote them | |
211 | to use them as constants in a program. An attempt to change their | |
0c6087a6 | 212 | values results in a @code{setting-constant} error. @xref{Constant |
83ac6b45 RS |
213 | Variables}. |
214 | ||
215 | @node Evaluation Notation | |
216 | @subsection Evaluation Notation | |
217 | @cindex evaluation notation | |
218 | @cindex documentation notation | |
0c6087a6 | 219 | @cindex notation |
83ac6b45 RS |
220 | |
221 | A Lisp expression that you can evaluate is called a @dfn{form}. | |
222 | Evaluating a form always produces a result, which is a Lisp object. In | |
223 | the examples in this manual, this is indicated with @samp{@result{}}: | |
224 | ||
225 | @example | |
226 | (car '(1 2)) | |
227 | @result{} 1 | |
228 | @end example | |
229 | ||
230 | @noindent | |
231 | You can read this as ``@code{(car '(1 2))} evaluates to 1''. | |
232 | ||
233 | When a form is a macro call, it expands into a new form for Lisp to | |
234 | evaluate. We show the result of the expansion with | |
a9f0a989 | 235 | @samp{@expansion{}}. We may or may not show the result of the |
83ac6b45 RS |
236 | evaluation of the expanded form. |
237 | ||
238 | @example | |
239 | (third '(a b c)) | |
240 | @expansion{} (car (cdr (cdr '(a b c)))) | |
241 | @result{} c | |
242 | @end example | |
243 | ||
7791402e | 244 | Sometimes to help describe one form we show another form that |
83ac6b45 RS |
245 | produces identical results. The exact equivalence of two forms is |
246 | indicated with @samp{@equiv{}}. | |
247 | ||
248 | @example | |
249 | (make-sparse-keymap) @equiv{} (list 'keymap) | |
250 | @end example | |
251 | ||
252 | @node Printing Notation | |
253 | @subsection Printing Notation | |
254 | @cindex printing notation | |
255 | ||
256 | Many of the examples in this manual print text when they are | |
7791402e RS |
257 | evaluated. If you execute example code in a Lisp Interaction buffer |
258 | (such as the buffer @samp{*scratch*}), the printed text is inserted into | |
259 | the buffer. If you execute the example by other means (such as by | |
260 | evaluating the function @code{eval-region}), the printed text is | |
79ddc9c9 | 261 | displayed in the echo area. |
83ac6b45 RS |
262 | |
263 | Examples in this manual indicate printed text with @samp{@print{}}, | |
8f40a868 RS |
264 | irrespective of where that text goes. The value returned by |
265 | evaluating the form (here @code{bar}) follows on a separate line with | |
266 | @samp{@result{}}. | |
83ac6b45 RS |
267 | |
268 | @example | |
269 | @group | |
5bacf5b6 | 270 | (progn (prin1 'foo) (princ "\n") (prin1 'bar)) |
83ac6b45 RS |
271 | @print{} foo |
272 | @print{} bar | |
273 | @result{} bar | |
274 | @end group | |
275 | @end example | |
276 | ||
277 | @node Error Messages | |
278 | @subsection Error Messages | |
279 | @cindex error message notation | |
280 | ||
281 | Some examples signal errors. This normally displays an error message | |
282 | in the echo area. We show the error message on a line starting with | |
283 | @samp{@error{}}. Note that @samp{@error{}} itself does not appear in | |
284 | the echo area. | |
285 | ||
286 | @example | |
287 | (+ 23 'x) | |
f9f59935 | 288 | @error{} Wrong type argument: number-or-marker-p, x |
83ac6b45 RS |
289 | @end example |
290 | ||
291 | @node Buffer Text Notation | |
292 | @subsection Buffer Text Notation | |
293 | @cindex buffer text notation | |
294 | ||
8241495d RS |
295 | Some examples describe modifications to the contents of a buffer, by |
296 | showing the ``before'' and ``after'' versions of the text. These | |
297 | examples show the contents of the buffer in question between two lines | |
298 | of dashes containing the buffer name. In addition, @samp{@point{}} | |
299 | indicates the location of point. (The symbol for point, of course, is | |
300 | not part of the text in the buffer; it indicates the place | |
301 | @emph{between} two characters where point is currently located.) | |
83ac6b45 RS |
302 | |
303 | @example | |
304 | ---------- Buffer: foo ---------- | |
305 | This is the @point{}contents of foo. | |
306 | ---------- Buffer: foo ---------- | |
307 | ||
308 | (insert "changed ") | |
309 | @result{} nil | |
310 | ---------- Buffer: foo ---------- | |
311 | This is the changed @point{}contents of foo. | |
312 | ---------- Buffer: foo ---------- | |
313 | @end example | |
314 | ||
315 | @node Format of Descriptions | |
316 | @subsection Format of Descriptions | |
317 | @cindex description format | |
318 | ||
319 | Functions, variables, macros, commands, user options, and special | |
320 | forms are described in this manual in a uniform format. The first | |
321 | line of a description contains the name of the item followed by its | |
322 | arguments, if any. | |
37680279 | 323 | @ifnottex |
83ac6b45 RS |
324 | The category---function, variable, or whatever---appears at the |
325 | beginning of the line. | |
37680279 | 326 | @end ifnottex |
83ac6b45 RS |
327 | @iftex |
328 | The category---function, variable, or whatever---is printed next to the | |
329 | right margin. | |
330 | @end iftex | |
331 | The description follows on succeeding lines, sometimes with examples. | |
332 | ||
333 | @menu | |
334 | * A Sample Function Description:: A description of an imaginary | |
335 | function, @code{foo}. | |
336 | * A Sample Variable Description:: A description of an imaginary | |
337 | variable, | |
177c0ea7 | 338 | @code{electric-future-map}. |
83ac6b45 RS |
339 | @end menu |
340 | ||
341 | @node A Sample Function Description | |
342 | @subsubsection A Sample Function Description | |
343 | @cindex function descriptions | |
344 | @cindex command descriptions | |
345 | @cindex macro descriptions | |
346 | @cindex special form descriptions | |
347 | ||
348 | In a function description, the name of the function being described | |
969fe9b5 RS |
349 | appears first. It is followed on the same line by a list of argument |
350 | names. These names are also used in the body of the description, to | |
351 | stand for the values of the arguments. | |
83ac6b45 | 352 | |
969fe9b5 RS |
353 | The appearance of the keyword @code{&optional} in the argument list |
354 | indicates that the subsequent arguments may be omitted (omitted | |
355 | arguments default to @code{nil}). Do not write @code{&optional} when | |
356 | you call the function. | |
83ac6b45 | 357 | |
0c6087a6 RS |
358 | The keyword @code{&rest} (which must be followed by a single |
359 | argument name) indicates that any number of arguments can follow. The | |
360 | single argument name following @code{&rest} will receive, as its | |
361 | value, a list of all the remaining arguments passed to the function. | |
362 | Do not write @code{&rest} when you call the function. | |
83ac6b45 RS |
363 | |
364 | Here is a description of an imaginary function @code{foo}: | |
365 | ||
366 | @defun foo integer1 &optional integer2 &rest integers | |
367 | The function @code{foo} subtracts @var{integer1} from @var{integer2}, | |
368 | then adds all the rest of the arguments to the result. If @var{integer2} | |
369 | is not supplied, then the number 19 is used by default. | |
370 | ||
371 | @example | |
372 | (foo 1 5 3 9) | |
373 | @result{} 16 | |
374 | (foo 5) | |
375 | @result{} 14 | |
376 | @end example | |
377 | ||
7dd3d99f | 378 | @need 1500 |
83ac6b45 RS |
379 | More generally, |
380 | ||
381 | @example | |
382 | (foo @var{w} @var{x} @var{y}@dots{}) | |
383 | @equiv{} | |
384 | (+ (- @var{x} @var{w}) @var{y}@dots{}) | |
385 | @end example | |
386 | @end defun | |
387 | ||
969fe9b5 | 388 | Any argument whose name contains the name of a type (e.g., |
83ac6b45 RS |
389 | @var{integer}, @var{integer1} or @var{buffer}) is expected to be of that |
390 | type. A plural of a type (such as @var{buffers}) often means a list of | |
969fe9b5 RS |
391 | objects of that type. Arguments named @var{object} may be of any type. |
392 | (@xref{Lisp Data Types}, for a list of Emacs object types.) Arguments | |
393 | with other sorts of names (e.g., @var{new-file}) are discussed | |
394 | specifically in the description of the function. In some sections, | |
395 | features common to the arguments of several functions are described at | |
396 | the beginning. | |
83ac6b45 RS |
397 | |
398 | @xref{Lambda Expressions}, for a more complete description of optional | |
399 | and rest arguments. | |
400 | ||
401 | Command, macro, and special form descriptions have the same format, | |
402 | but the word `Function' is replaced by `Command', `Macro', or `Special | |
403 | Form', respectively. Commands are simply functions that may be called | |
404 | interactively; macros process their arguments differently from functions | |
405 | (the arguments are not evaluated), but are presented the same way. | |
406 | ||
407 | Special form descriptions use a more complex notation to specify | |
969fe9b5 | 408 | optional and repeated arguments because they can break the argument |
83ac6b45 | 409 | list down into separate arguments in more complicated ways. |
a9f0a989 | 410 | @samp{@r{[}@var{optional-arg}@r{]}} means that @var{optional-arg} is |
83ac6b45 RS |
411 | optional and @samp{@var{repeated-args}@dots{}} stands for zero or more |
412 | arguments. Parentheses are used when several arguments are grouped into | |
413 | additional levels of list structure. Here is an example: | |
414 | ||
415 | @defspec count-loop (@var{var} [@var{from} @var{to} [@var{inc}]]) @var{body}@dots{} | |
416 | This imaginary special form implements a loop that executes the | |
417 | @var{body} forms and then increments the variable @var{var} on each | |
418 | iteration. On the first iteration, the variable has the value | |
a9f0a989 | 419 | @var{from}; on subsequent iterations, it is incremented by one (or by |
83ac6b45 RS |
420 | @var{inc} if that is given). The loop exits before executing @var{body} |
421 | if @var{var} equals @var{to}. Here is an example: | |
422 | ||
423 | @example | |
424 | (count-loop (i 0 10) | |
425 | (prin1 i) (princ " ") | |
969fe9b5 RS |
426 | (prin1 (aref vector i)) |
427 | (terpri)) | |
83ac6b45 RS |
428 | @end example |
429 | ||
a9f0a989 | 430 | If @var{from} and @var{to} are omitted, @var{var} is bound to |
83ac6b45 RS |
431 | @code{nil} before the loop begins, and the loop exits if @var{var} is |
432 | non-@code{nil} at the beginning of an iteration. Here is an example: | |
433 | ||
434 | @example | |
435 | (count-loop (done) | |
436 | (if (pending) | |
437 | (fixit) | |
438 | (setq done t))) | |
439 | @end example | |
440 | ||
441 | In this special form, the arguments @var{from} and @var{to} are | |
442 | optional, but must both be present or both absent. If they are present, | |
443 | @var{inc} may optionally be specified as well. These arguments are | |
444 | grouped with the argument @var{var} into a list, to distinguish them | |
445 | from @var{body}, which includes all remaining elements of the form. | |
446 | @end defspec | |
447 | ||
448 | @node A Sample Variable Description | |
449 | @subsubsection A Sample Variable Description | |
450 | @cindex variable descriptions | |
451 | @cindex option descriptions | |
452 | ||
0c6087a6 RS |
453 | A @dfn{variable} is a name that can hold a value. Although nearly |
454 | all variables can be set by the user, certain variables exist | |
455 | specifically so that users can change them; these are called @dfn{user | |
83ac6b45 RS |
456 | options}. Ordinary variables and user options are described using a |
457 | format like that for functions except that there are no arguments. | |
458 | ||
459 | Here is a description of the imaginary @code{electric-future-map} | |
460 | variable.@refill | |
461 | ||
462 | @defvar electric-future-map | |
463 | The value of this variable is a full keymap used by Electric Command | |
464 | Future mode. The functions in this map allow you to edit commands you | |
465 | have not yet thought about executing. | |
466 | @end defvar | |
467 | ||
468 | User option descriptions have the same format, but `Variable' is | |
469 | replaced by `User Option'. | |
470 | ||
969fe9b5 RS |
471 | @node Version Info |
472 | @section Version Information | |
473 | ||
a9f0a989 RS |
474 | These facilities provide information about which version of Emacs is |
475 | in use. | |
969fe9b5 | 476 | |
8bbf587d | 477 | @deffn Command emacs-version &optional here |
969fe9b5 RS |
478 | This function returns a string describing the version of Emacs that is |
479 | running. It is useful to include this string in bug reports. | |
480 | ||
a9f0a989 | 481 | @smallexample |
969fe9b5 RS |
482 | @group |
483 | (emacs-version) | |
484 | @result{} "GNU Emacs 20.3.5 (i486-pc-linux-gnulibc1, X toolkit) | |
485 | of Sat Feb 14 1998 on psilocin.gnu.org" | |
486 | @end group | |
a9f0a989 | 487 | @end smallexample |
969fe9b5 | 488 | |
8bbf587d RS |
489 | If @var{here} is non-@code{nil}, it inserts the text in the buffer |
490 | before point, and returns @code{nil}. Called interactively, the | |
491 | function prints the same information in the echo area, but giving a | |
492 | prefix argument makes @var{here} non-@code{nil}. | |
969fe9b5 RS |
493 | @end deffn |
494 | ||
495 | @defvar emacs-build-time | |
a9f0a989 RS |
496 | The value of this variable indicates the time at which Emacs was built |
497 | at the local site. It is a list of three integers, like the value | |
498 | of @code{current-time} (@pxref{Time of Day}). | |
969fe9b5 RS |
499 | |
500 | @example | |
501 | @group | |
502 | emacs-build-time | |
a9f0a989 | 503 | @result{} (13623 62065 344633) |
969fe9b5 RS |
504 | @end group |
505 | @end example | |
506 | @end defvar | |
507 | ||
508 | @defvar emacs-version | |
509 | The value of this variable is the version of Emacs being run. It is a | |
510 | string such as @code{"20.3.1"}. The last number in this string is not | |
511 | really part of the Emacs release version number; it is incremented each | |
aab28c42 | 512 | time you build Emacs in any given directory. A value with four numeric |
8241495d RS |
513 | components, such as @code{"20.3.9.1"}, indicates an unreleased test |
514 | version. | |
969fe9b5 RS |
515 | @end defvar |
516 | ||
a9f0a989 | 517 | The following two variables have existed since Emacs version 19.23: |
969fe9b5 RS |
518 | |
519 | @defvar emacs-major-version | |
520 | The major version number of Emacs, as an integer. For Emacs version | |
521 | 20.3, the value is 20. | |
522 | @end defvar | |
523 | ||
524 | @defvar emacs-minor-version | |
525 | The minor version number of Emacs, as an integer. For Emacs version | |
526 | 20.3, the value is 3. | |
527 | @end defvar | |
528 | ||
83ac6b45 RS |
529 | @node Acknowledgements |
530 | @section Acknowledgements | |
531 | ||
532 | This manual was written by Robert Krawitz, Bil Lewis, Dan LaLiberte, | |
533 | Richard M. Stallman and Chris Welty, the volunteers of the GNU manual | |
534 | group, in an effort extending over several years. Robert J. Chassell | |
535 | helped to review and edit the manual, with the support of the Defense | |
536 | Advanced Research Projects Agency, ARPA Order 6082, arranged by Warren | |
a40d4712 | 537 | A. Hunt, Jr.@: of Computational Logic, Inc. |
83ac6b45 RS |
538 | |
539 | Corrections were supplied by Karl Berry, Jim Blandy, Bard Bloom, | |
540 | Stephane Boucher, David Boyes, Alan Carroll, Richard Davis, Lawrence | |
541 | R. Dodd, Peter Doornbosch, David A. Duff, Chris Eich, Beverly | |
542 | Erlebacher, David Eckelkamp, Ralf Fassel, Eirik Fuller, Stephen Gildea, | |
543 | Bob Glickstein, Eric Hanchrow, George Hartzell, Nathan Hess, Masayuki | |
544 | Ida, Dan Jacobson, Jak Kirman, Bob Knighten, Frederick M. Korz, Joe | |
545 | Lammens, Glenn M. Lewis, K. Richard Magill, Brian Marick, Roland | |
546 | McGrath, Skip Montanaro, John Gardiner Myers, Thomas A. Peterson, | |
547 | Francesco Potorti, Friedrich Pukelsheim, Arnold D. Robbins, Raul | |
a40d4712 | 548 | Rockwell, Per Starb@"ack, Shinichirou Sugou, Kimmo Suominen, Edward Tharp, |
83ac6b45 RS |
549 | Bill Trost, Rickard Westman, Jean White, Matthew Wilding, Carl Witty, |
550 | Dale Worley, Rusty Wright, and David D. Zuhn. | |
ab5796a9 MB |
551 | |
552 | @ignore | |
553 | arch-tag: d156593f-82f8-4708-a844-204e48f7f2aa | |
554 | @end ignore |