intro.texi 21.4 KB
Newer Older
Richard M. Stallman's avatar
Richard M. Stallman committed
1 2
@c -*-texinfo-*-
@c This is part of the GNU Emacs Lisp Reference Manual.
3 4
@c Copyright (C) 1990, 1991, 1992, 1993, 1994, 2001, 2002, 2003, 2004,
@c   2005, 2006, 2007  Free Software Foundation, Inc.
Richard M. Stallman's avatar
Richard M. Stallman committed
5 6 7
@c See the file elisp.texi for copying conditions.
@setfilename ../info/intro

Gerd Moellmann's avatar
Gerd Moellmann committed
8
@node Introduction, Lisp Data Types, Top, Top
Richard M. Stallman's avatar
Richard M. Stallman committed
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
@comment  node-name,  next,  previous,  up
@chapter Introduction

  Most of the GNU Emacs text editor is written in the programming
language called Emacs Lisp.  You can write new code in Emacs Lisp and
install it as an extension to the editor.  However, Emacs Lisp is more
than a mere ``extension language''; it is a full computer programming
language in its own right.  You can use it as you would any other
programming language.

  Because Emacs Lisp is designed for use in an editor, it has special
features for scanning and parsing text as well as features for handling
files, buffers, displays, subprocesses, and so on.  Emacs Lisp is
closely integrated with the editing facilities; thus, editing commands
are functions that can also conveniently be called from Lisp programs,
and parameters for customization are ordinary Lisp variables.

26 27 28 29 30 31 32 33 34 35 36
  This manual attempts to be a full description of Emacs Lisp.  For a
beginner's introduction to Emacs Lisp, see @cite{An Introduction to
Emacs Lisp Programming}, by Bob Chassell, also published by the Free
Software Foundation.  This manual presumes considerable familiarity with
the use of Emacs for editing; see @cite{The GNU Emacs Manual} for this
basic information.

  Generally speaking, the earlier chapters describe features of Emacs
Lisp that have counterparts in many programming languages, and later
chapters describe features that are peculiar to Emacs Lisp or relate
specifically to editing.
Richard M. Stallman's avatar
Richard M. Stallman committed
37

38 39
  This is edition @value{VERSION} of the GNU Emacs Lisp Reference
Manual, corresponding to Emacs version @value{EMACSVER}.
Richard M. Stallman's avatar
Richard M. Stallman committed
40 41 42 43 44

@menu
* Caveats::             Flaws and a request for help.
* Lisp History::        Emacs Lisp is descended from Maclisp.
* Conventions::         How the manual is formatted.
45
* Version Info::        Which Emacs version is running?
Richard M. Stallman's avatar
Richard M. Stallman committed
46 47 48 49 50
* Acknowledgements::    The authors, editors, and sponsors of this manual.
@end menu

@node Caveats
@section Caveats
Richard M. Stallman's avatar
Richard M. Stallman committed
51
@cindex bugs in this manual
Richard M. Stallman's avatar
Richard M. Stallman committed
52 53

  This manual has gone through numerous drafts.  It is nearly complete
Richard M. Stallman's avatar
Richard M. Stallman committed
54 55 56 57 58
but not flawless.  There are a few topics that are not covered, either
because we consider them secondary (such as most of the individual
modes) or because they are yet to be written.  Because we are not able
to deal with them completely, we have left out several parts
intentionally.  This includes most information about usage on VMS.
Richard M. Stallman's avatar
Richard M. Stallman committed
59 60 61 62 63 64 65 66 67

  The manual should be fully correct in what it does cover, and it is
therefore open to criticism on anything it says---from specific examples
and descriptive text, to the ordering of chapters and sections.  If
something is confusing, or you find that you have to look at the sources
or experiment to learn something not covered in the manual, then perhaps
the manual should be fixed.  Please let us know.

@iftex
Phillip Rulon's avatar
Phillip Rulon committed
68 69
  As you use this manual, we ask that you mark pages with corrections so
you can later look them up and send them to us.  If you think of a simple,
Richard M. Stallman's avatar
Richard M. Stallman committed
70
real-life example for a function or group of functions, please make an
Richard M. Stallman's avatar
Richard M. Stallman committed
71 72
effort to write it up and send it in.  Please reference any comments to
the chapter name, section name, and function name, as appropriate, since
Richard M. Stallman's avatar
Richard M. Stallman committed
73 74 75
page numbers and chapter and section numbers will change and we may have
trouble finding the text you are talking about.  Also state the number
of the edition you are criticizing.
Richard M. Stallman's avatar
Richard M. Stallman committed
76
@end iftex
Gerd Moellmann's avatar
Gerd Moellmann committed
77
@ifnottex
Richard M. Stallman's avatar
Richard M. Stallman committed
78 79 80 81 82 83

As you use this manual, we ask that you send corrections as soon as you
find them.  If you think of a simple, real life example for a function
or group of functions, please make an effort to write it up and send it
in.  Please reference any comments to the node name and function or
variable name, as appropriate.  Also state the number of the edition
Phillip Rulon's avatar
Phillip Rulon committed
84
you are criticizing.
Gerd Moellmann's avatar
Gerd Moellmann committed
85
@end ifnottex
Richard M. Stallman's avatar
Richard M. Stallman committed
86

Richard M. Stallman's avatar
Richard M. Stallman committed
87 88
@cindex bugs
@cindex suggestions
Richard M. Stallman's avatar
Richard M. Stallman committed
89 90 91
Please mail comments and corrections to

@example
92
bug-lisp-manual@@gnu.org
Richard M. Stallman's avatar
Richard M. Stallman committed
93 94 95 96 97 98 99 100
@end example

@noindent
We let mail to this list accumulate unread until someone decides to
apply the corrections.  Months, and sometimes years, go by between
updates.  So please attach no significance to the lack of a reply---your
mail @emph{will} be acted on in due time.  If you want to contact the
Emacs maintainers more quickly, send mail to
101
@code{bug-gnu-emacs@@gnu.org}.
Richard M. Stallman's avatar
Richard M. Stallman committed
102 103 104 105 106

@node Lisp History
@section Lisp History
@cindex Lisp history

107
  Lisp (LISt Processing language) was first developed in the late 1950s
Richard M. Stallman's avatar
Richard M. Stallman committed
108
at the Massachusetts Institute of Technology for research in artificial
109
intelligence.  The great power of the Lisp language makes it ideal
Richard M. Stallman's avatar
Richard M. Stallman committed
110 111 112 113 114 115
for other purposes as well, such as writing editing commands.

@cindex Maclisp
@cindex Common Lisp
  Dozens of Lisp implementations have been built over the years, each
with its own idiosyncrasies.  Many of them were inspired by Maclisp,
116
which was written in the 1960s at MIT's Project MAC.  Eventually the
Richard M. Stallman's avatar
Richard M. Stallman committed
117
implementors of the descendants of Maclisp came together and developed a
118
standard for Lisp systems, called Common Lisp.  In the meantime, Gerry
119 120
Sussman and Guy Steele at MIT developed a simplified but very powerful
dialect of Lisp, called Scheme.
Richard M. Stallman's avatar
Richard M. Stallman committed
121 122 123

  GNU Emacs Lisp is largely inspired by Maclisp, and a little by Common
Lisp.  If you know Common Lisp, you will notice many similarities.
124
However, many features of Common Lisp have been omitted or
Richard M. Stallman's avatar
Richard M. Stallman committed
125 126 127 128 129 130
simplified in order to reduce the memory requirements of GNU Emacs.
Sometimes the simplifications are so drastic that a Common Lisp user
might be very confused.  We will occasionally point out how GNU Emacs
Lisp differs from Common Lisp.  If you don't know Common Lisp, don't
worry about it; this manual is self-contained.

131 132
@pindex cl
  A certain amount of Common Lisp emulation is available via the
133
@file{cl} library.  @inforef{Top, Overview, cl}.
134

135
  Emacs Lisp is not at all influenced by Scheme; but the GNU project has
136 137
an implementation of Scheme, called Guile.  We use Guile in all new GNU
software that calls for extensibility.
138

Richard M. Stallman's avatar
Richard M. Stallman committed
139 140 141 142 143 144 145 146 147 148
@node Conventions
@section Conventions

This section explains the notational conventions that are used in this
manual.  You may want to skip this section and refer back to it later.

@menu
* Some Terms::               Explanation of terms we use in this manual.
* nil and t::                How the symbols @code{nil} and @code{t} are used.
* Evaluation Notation::      The format we use for examples of evaluation.
149
* Printing Notation::        The format we use when examples print text.
Richard M. Stallman's avatar
Richard M. Stallman committed
150 151 152 153 154 155 156 157 158
* Error Messages::           The format we use for examples of errors.
* Buffer Text Notation::     The format we use for buffer contents in examples.
* Format of Descriptions::   Notation for describing functions, variables, etc.
@end menu

@node Some Terms
@subsection Some Terms

  Throughout this manual, the phrases ``the Lisp reader'' and ``the Lisp
159 160
printer'' refer to those routines in Lisp that convert textual
representations of Lisp objects into actual Lisp objects, and vice
Richard M. Stallman's avatar
Richard M. Stallman committed
161 162
versa.  @xref{Printed Representation}, for more details.  You, the
person reading this manual, are thought of as ``the programmer'' and are
163
addressed as ``you.''  ``The user'' is the person who uses Lisp
164
programs, including those you write.
Richard M. Stallman's avatar
Richard M. Stallman committed
165

Richard M. Stallman's avatar
Richard M. Stallman committed
166
@cindex fonts in this manual
167 168 169
  Examples of Lisp code are formatted like this: @code{(list 1 2 3)}.
Names that represent metasyntactic variables, or arguments to a function
being described, are formatted like this: @var{first-number}.
Richard M. Stallman's avatar
Richard M. Stallman committed
170 171 172 173 174 175

@node nil and t
@subsection @code{nil} and @code{t}
@cindex truth value
@cindex boolean

Eli Zaretskii's avatar
Eli Zaretskii committed
176 177
@cindex @code{nil}
@cindex false
Karl Heuer's avatar
Karl Heuer committed
178
  In Lisp, the symbol @code{nil} has three separate meanings: it
Richard M. Stallman's avatar
Richard M. Stallman committed
179 180 181 182 183 184 185 186 187 188 189
is a symbol with the name @samp{nil}; it is the logical truth value
@var{false}; and it is the empty list---the list of zero elements.
When used as a variable, @code{nil} always has the value @code{nil}.

  As far as the Lisp reader is concerned, @samp{()} and @samp{nil} are
identical: they stand for the same object, the symbol @code{nil}.  The
different ways of writing the symbol are intended entirely for human
readers.  After the Lisp reader has read either @samp{()} or @samp{nil},
there is no way to determine which representation was actually written
by the programmer.

Richard M. Stallman's avatar
Richard M. Stallman committed
190 191
  In this manual, we write @code{()} when we wish to emphasize that it
means the empty list, and we write @code{nil} when we wish to emphasize
Richard M. Stallman's avatar
Richard M. Stallman committed
192 193 194 195 196
that it means the truth value @var{false}.  That is a good convention to use
in Lisp programs also.

@example
(cons 'foo ())                ; @r{Emphasize the empty list}
Richard M. Stallman's avatar
Richard M. Stallman committed
197
(setq foo-flag nil)           ; @r{Emphasize the truth value @var{false}}
Richard M. Stallman's avatar
Richard M. Stallman committed
198 199
@end example

Eli Zaretskii's avatar
Eli Zaretskii committed
200
@cindex @code{t}
Richard M. Stallman's avatar
Richard M. Stallman committed
201 202 203 204 205
@cindex true
  In contexts where a truth value is expected, any non-@code{nil} value
is considered to be @var{true}.  However, @code{t} is the preferred way
to represent the truth value @var{true}.  When you need to choose a
value which represents @var{true}, and there is no other basis for
206 207
choosing, use @code{t}.  The symbol @code{t} always has the value
@code{t}.
Richard M. Stallman's avatar
Richard M. Stallman committed
208 209 210 211

  In Emacs Lisp, @code{nil} and @code{t} are special symbols that always
evaluate to themselves.  This is so that you do not need to quote them
to use them as constants in a program.  An attempt to change their
212
values results in a @code{setting-constant} error.  @xref{Constant
Richard M. Stallman's avatar
Richard M. Stallman committed
213 214
Variables}.

215
@defun booleanp object
216
Return non-nil if @var{object} is one of the two canonical boolean
217 218 219
values: @code{t} or @code{nil}.
@end defun

Richard M. Stallman's avatar
Richard M. Stallman committed
220 221 222 223
@node Evaluation Notation
@subsection Evaluation Notation
@cindex evaluation notation
@cindex documentation notation
224
@cindex notation
Richard M. Stallman's avatar
Richard M. Stallman committed
225 226 227 228 229 230 231 232 233 234 235

  A Lisp expression that you can evaluate is called a @dfn{form}.
Evaluating a form always produces a result, which is a Lisp object.  In
the examples in this manual, this is indicated with @samp{@result{}}:

@example
(car '(1 2))
     @result{} 1
@end example

@noindent
236
You can read this as ``@code{(car '(1 2))} evaluates to 1.''
Richard M. Stallman's avatar
Richard M. Stallman committed
237 238 239

  When a form is a macro call, it expands into a new form for Lisp to
evaluate.  We show the result of the expansion with
240
@samp{@expansion{}}.  We may or may not show the result of the
Richard M. Stallman's avatar
Richard M. Stallman committed
241 242 243 244 245 246 247 248
evaluation of the expanded form.

@example
(third '(a b c))
     @expansion{} (car (cdr (cdr '(a b c))))
     @result{} c
@end example

Richard M. Stallman's avatar
Richard M. Stallman committed
249
  Sometimes to help describe one form we show another form that
Richard M. Stallman's avatar
Richard M. Stallman committed
250 251 252 253 254 255 256 257 258 259 260 261
produces identical results.  The exact equivalence of two forms is
indicated with @samp{@equiv{}}.

@example
(make-sparse-keymap) @equiv{} (list 'keymap)
@end example

@node Printing Notation
@subsection Printing Notation
@cindex printing notation

  Many of the examples in this manual print text when they are
Richard M. Stallman's avatar
Richard M. Stallman committed
262 263 264 265
evaluated.  If you execute example code in a Lisp Interaction buffer
(such as the buffer @samp{*scratch*}), the printed text is inserted into
the buffer.  If you execute the example by other means (such as by
evaluating the function @code{eval-region}), the printed text is
Gerd Moellmann's avatar
Gerd Moellmann committed
266
displayed in the echo area.
Richard M. Stallman's avatar
Richard M. Stallman committed
267 268

  Examples in this manual indicate printed text with @samp{@print{}},
269 270 271
irrespective of where that text goes.  The value returned by
evaluating the form (here @code{bar}) follows on a separate line with
@samp{@result{}}.
Richard M. Stallman's avatar
Richard M. Stallman committed
272 273 274

@example
@group
275
(progn (prin1 'foo) (princ "\n") (prin1 'bar))
Richard M. Stallman's avatar
Richard M. Stallman committed
276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292
     @print{} foo
     @print{} bar
     @result{} bar
@end group
@end example

@node Error Messages
@subsection Error Messages
@cindex error message notation

  Some examples signal errors.  This normally displays an error message
in the echo area.  We show the error message on a line starting with
@samp{@error{}}.  Note that @samp{@error{}} itself does not appear in
the echo area.

@example
(+ 23 'x)
293
@error{} Wrong type argument: number-or-marker-p, x
Richard M. Stallman's avatar
Richard M. Stallman committed
294 295 296 297 298 299
@end example

@node Buffer Text Notation
@subsection Buffer Text Notation
@cindex buffer text notation

300 301 302 303 304 305 306
  Some examples describe modifications to the contents of a buffer, by
showing the ``before'' and ``after'' versions of the text.  These
examples show the contents of the buffer in question between two lines
of dashes containing the buffer name.  In addition, @samp{@point{}}
indicates the location of point.  (The symbol for point, of course, is
not part of the text in the buffer; it indicates the place
@emph{between} two characters where point is currently located.)
Richard M. Stallman's avatar
Richard M. Stallman committed
307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327

@example
---------- Buffer: foo ----------
This is the @point{}contents of foo.
---------- Buffer: foo ----------

(insert "changed ")
     @result{} nil
---------- Buffer: foo ----------
This is the changed @point{}contents of foo.
---------- Buffer: foo ----------
@end example

@node Format of Descriptions
@subsection Format of Descriptions
@cindex description format

  Functions, variables, macros, commands, user options, and special
forms are described in this manual in a uniform format.  The first
line of a description contains the name of the item followed by its
arguments, if any.
Gerd Moellmann's avatar
Gerd Moellmann committed
328
@ifnottex
Richard M. Stallman's avatar
Richard M. Stallman committed
329 330
The category---function, variable, or whatever---appears at the
beginning of the line.
Gerd Moellmann's avatar
Gerd Moellmann committed
331
@end ifnottex
Richard M. Stallman's avatar
Richard M. Stallman committed
332 333 334 335 336 337 338 339 340 341 342
@iftex
The category---function, variable, or whatever---is printed next to the
right margin.
@end iftex
The description follows on succeeding lines, sometimes with examples.

@menu
* A Sample Function Description::       A description of an imaginary
                                          function, @code{foo}.
* A Sample Variable Description::       A description of an imaginary
                                          variable,
343
                                          @code{electric-future-map}.
Richard M. Stallman's avatar
Richard M. Stallman committed
344 345 346 347 348 349 350 351 352 353
@end menu

@node A Sample Function Description
@subsubsection A Sample Function Description
@cindex function descriptions
@cindex command descriptions
@cindex macro descriptions
@cindex special form descriptions

  In a function description, the name of the function being described
354 355 356
appears first.  It is followed on the same line by a list of argument
names.  These names are also used in the body of the description, to
stand for the values of the arguments.
Richard M. Stallman's avatar
Richard M. Stallman committed
357

358 359 360 361
  The appearance of the keyword @code{&optional} in the argument list
indicates that the subsequent arguments may be omitted (omitted
arguments default to @code{nil}).  Do not write @code{&optional} when
you call the function.
Richard M. Stallman's avatar
Richard M. Stallman committed
362

363 364 365 366 367
  The keyword @code{&rest} (which must be followed by a single
argument name) indicates that any number of arguments can follow.  The
single argument name following @code{&rest} will receive, as its
value, a list of all the remaining arguments passed to the function.
Do not write @code{&rest} when you call the function.
Richard M. Stallman's avatar
Richard M. Stallman committed
368 369 370 371 372 373 374 375 376 377 378 379 380 381 382

  Here is a description of an imaginary function @code{foo}:

@defun foo integer1 &optional integer2 &rest integers
The function @code{foo} subtracts @var{integer1} from @var{integer2},
then adds all the rest of the arguments to the result.  If @var{integer2}
is not supplied, then the number 19 is used by default.

@example
(foo 1 5 3 9)
     @result{} 16
(foo 5)
     @result{} 14
@end example

383
@need 1500
Richard M. Stallman's avatar
Richard M. Stallman committed
384 385 386 387 388 389 390 391 392
More generally,

@example
(foo @var{w} @var{x} @var{y}@dots{})
@equiv{}
(+ (- @var{x} @var{w}) @var{y}@dots{})
@end example
@end defun

393
  Any argument whose name contains the name of a type (e.g.,
Richard M. Stallman's avatar
Richard M. Stallman committed
394 395
@var{integer}, @var{integer1} or @var{buffer}) is expected to be of that
type.  A plural of a type (such as @var{buffers}) often means a list of
396 397 398 399 400 401
objects of that type.  Arguments named @var{object} may be of any type.
(@xref{Lisp Data Types}, for a list of Emacs object types.)  Arguments
with other sorts of names (e.g., @var{new-file}) are discussed
specifically in the description of the function.  In some sections,
features common to the arguments of several functions are described at
the beginning.
Richard M. Stallman's avatar
Richard M. Stallman committed
402 403 404 405 406 407 408 409 410 411 412

  @xref{Lambda Expressions}, for a more complete description of optional
and rest arguments.

  Command, macro, and special form descriptions have the same format,
but the word `Function' is replaced by `Command', `Macro', or `Special
Form', respectively.  Commands are simply functions that may be called
interactively; macros process their arguments differently from functions
(the arguments are not evaluated), but are presented the same way.

  Special form descriptions use a more complex notation to specify
413
optional and repeated arguments because they can break the argument
Richard M. Stallman's avatar
Richard M. Stallman committed
414
list down into separate arguments in more complicated ways.
415
@samp{@r{[}@var{optional-arg}@r{]}} means that @var{optional-arg} is
Richard M. Stallman's avatar
Richard M. Stallman committed
416 417 418 419 420 421 422 423
optional and @samp{@var{repeated-args}@dots{}} stands for zero or more
arguments.  Parentheses are used when several arguments are grouped into
additional levels of list structure.  Here is an example:

@defspec count-loop (@var{var} [@var{from} @var{to} [@var{inc}]]) @var{body}@dots{}
This imaginary special form implements a loop that executes the
@var{body} forms and then increments the variable @var{var} on each
iteration.  On the first iteration, the variable has the value
424
@var{from}; on subsequent iterations, it is incremented by one (or by
Richard M. Stallman's avatar
Richard M. Stallman committed
425 426 427 428 429 430
@var{inc} if that is given).  The loop exits before executing @var{body}
if @var{var} equals @var{to}.  Here is an example:

@example
(count-loop (i 0 10)
  (prin1 i) (princ " ")
431 432
  (prin1 (aref vector i))
  (terpri))
Richard M. Stallman's avatar
Richard M. Stallman committed
433 434
@end example

435
If @var{from} and @var{to} are omitted, @var{var} is bound to
Richard M. Stallman's avatar
Richard M. Stallman committed
436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457
@code{nil} before the loop begins, and the loop exits if @var{var} is
non-@code{nil} at the beginning of an iteration.  Here is an example:

@example
(count-loop (done)
  (if (pending)
      (fixit)
    (setq done t)))
@end example

In this special form, the arguments @var{from} and @var{to} are
optional, but must both be present or both absent.  If they are present,
@var{inc} may optionally be specified as well.  These arguments are
grouped with the argument @var{var} into a list, to distinguish them
from @var{body}, which includes all remaining elements of the form.
@end defspec

@node A Sample Variable Description
@subsubsection A Sample Variable Description
@cindex variable descriptions
@cindex option descriptions

458 459 460
  A @dfn{variable} is a name that can hold a value.  Although nearly
all variables can be set by the user, certain variables exist
specifically so that users can change them; these are called @dfn{user
Richard M. Stallman's avatar
Richard M. Stallman committed
461 462 463 464 465 466 467 468 469 470 471 472 473 474 475
options}.  Ordinary variables and user options are described using a
format like that for functions except that there are no arguments.

  Here is a description of the imaginary @code{electric-future-map}
variable.@refill

@defvar electric-future-map
The value of this variable is a full keymap used by Electric Command
Future mode.  The functions in this map allow you to edit commands you
have not yet thought about executing.
@end defvar

  User option descriptions have the same format, but `Variable' is
replaced by `User Option'.

476 477 478
@node Version Info
@section Version Information

479 480
  These facilities provide information about which version of Emacs is
in use.
481

482
@deffn Command emacs-version &optional here
483 484 485
This function returns a string describing the version of Emacs that is
running.  It is useful to include this string in bug reports.

486
@smallexample
487 488 489 490 491
@group
(emacs-version)
  @result{} "GNU Emacs 20.3.5 (i486-pc-linux-gnulibc1, X toolkit)
 of Sat Feb 14 1998 on psilocin.gnu.org"
@end group
492
@end smallexample
493

494 495 496 497
If @var{here} is non-@code{nil}, it inserts the text in the buffer
before point, and returns @code{nil}.  Called interactively, the
function prints the same information in the echo area, but giving a
prefix argument makes @var{here} non-@code{nil}.
498 499 500
@end deffn

@defvar emacs-build-time
501 502 503
The value of this variable indicates the time at which Emacs was built
at the local site.  It is a list of three integers, like the value
of @code{current-time} (@pxref{Time of Day}).
504 505 506 507

@example
@group
emacs-build-time
508
     @result{} (13623 62065 344633)
509 510 511 512 513 514 515 516
@end group
@end example
@end defvar

@defvar emacs-version
The value of this variable is the version of Emacs being run.  It is a
string such as @code{"20.3.1"}.  The last number in this string is not
really part of the Emacs release version number; it is incremented each
Richard M. Stallman's avatar
Richard M. Stallman committed
517
time you build Emacs in any given directory.  A value with four numeric
518 519
components, such as @code{"20.3.9.1"}, indicates an unreleased test
version.
520 521
@end defvar

522
  The following two variables have existed since Emacs version 19.23:
523 524 525 526 527 528 529 530 531 532 533

@defvar emacs-major-version
The major version number of Emacs, as an integer.  For Emacs version
20.3, the value is 20.
@end defvar

@defvar emacs-minor-version
The minor version number of Emacs, as an integer.  For Emacs version
20.3, the value is 3.
@end defvar

Richard M. Stallman's avatar
Richard M. Stallman committed
534 535 536 537
@node Acknowledgements
@section Acknowledgements

  This manual was written by Robert Krawitz, Bil Lewis, Dan LaLiberte,
Karl Berry's avatar
Karl Berry committed
538 539 540 541 542 543
Richard@tie{}M. Stallman and Chris Welty, the volunteers of the GNU
manual group, in an effort extending over several years.
Robert@tie{}J. Chassell helped to review and edit the manual, with the
support of the Defense Advanced Research Projects Agency, ARPA Order
6082, arranged by Warren@tie{}A. Hunt, Jr.@: of Computational Logic,
Inc.
Richard M. Stallman's avatar
Richard M. Stallman committed
544 545 546 547 548 549 550 551 552 553

  Corrections were supplied by Karl Berry, Jim Blandy, Bard Bloom,
Stephane Boucher, David Boyes, Alan Carroll, Richard Davis, Lawrence
R. Dodd, Peter Doornbosch, David A. Duff, Chris Eich, Beverly
Erlebacher, David Eckelkamp, Ralf Fassel, Eirik Fuller, Stephen Gildea,
Bob Glickstein, Eric Hanchrow, George Hartzell, Nathan Hess, Masayuki
Ida, Dan Jacobson, Jak Kirman, Bob Knighten, Frederick M. Korz, Joe
Lammens, Glenn M. Lewis, K. Richard Magill, Brian Marick, Roland
McGrath, Skip Montanaro, John Gardiner Myers, Thomas A. Peterson,
Francesco Potorti, Friedrich Pukelsheim, Arnold D. Robbins, Raul
Phillip Rulon's avatar
Phillip Rulon committed
554
Rockwell, Per Starb@"ack, Shinichirou Sugou, Kimmo Suominen, Edward Tharp,
Richard M. Stallman's avatar
Richard M. Stallman committed
555 556
Bill Trost, Rickard Westman, Jean White, Matthew Wilding, Carl Witty,
Dale Worley, Rusty Wright, and David D. Zuhn.
Miles Bader's avatar
Miles Bader committed
557 558 559 560

@ignore
   arch-tag: d156593f-82f8-4708-a844-204e48f7f2aa
@end ignore