2 @c This is part of the GNU Emacs Lisp Reference Manual.
3 @c Copyright (C) 1990-1995, 1998-1999, 2001-2012 Free Software Foundation, Inc.
4 @c See the file elisp.texi for copying conditions.
8 @cindex element (of list)
10 A @dfn{list} represents a sequence of zero or more elements (which may
11 be any Lisp objects). The important difference between lists and
12 vectors is that two or more lists can share part of their structure; in
13 addition, you can insert or delete elements in a list without copying
17 * Cons Cells:: How lists are made out of cons cells.
18 * List-related Predicates:: Is this object a list? Comparing two lists.
19 * List Elements:: Extracting the pieces of a list.
20 * Building Lists:: Creating list structure.
21 * List Variables:: Modifying lists stored in variables.
22 * Modifying Lists:: Storing new pieces into an existing list.
23 * Sets And Lists:: A list can represent a finite mathematical set.
24 * Association Lists:: A list can represent a finite relation or mapping.
28 @section Lists and Cons Cells
29 @cindex lists and cons cells
31 Lists in Lisp are not a primitive data type; they are built up from
32 @dfn{cons cells} (@pxref{Cons Cell Type}). A cons cell is a data
33 object that represents an ordered pair. That is, it has two slots,
34 and each slot @dfn{holds}, or @dfn{refers to}, some Lisp object. One
35 slot is known as the @sc{car}, and the other is known as the @sc{cdr}.
36 (These names are traditional; see @ref{Cons Cell Type}.) @sc{cdr} is
37 pronounced ``could-er''.
39 We say that ``the @sc{car} of this cons cell is'' whatever object
40 its @sc{car} slot currently holds, and likewise for the @sc{cdr}.
42 A list is a series of cons cells ``chained together'', so that each
43 cell refers to the next one. There is one cons cell for each element
44 of the list. By convention, the @sc{car}s of the cons cells hold the
45 elements of the list, and the @sc{cdr}s are used to chain the list
46 (this asymmetry between @sc{car} and @sc{cdr} is entirely a matter of
47 convention; at the level of cons cells, the @sc{car} and @sc{cdr}
48 slots have similar properties). Hence, the @sc{cdr} slot of each cons
49 cell in a list refers to the following cons cell.
52 Also by convention, the @sc{cdr} of the last cons cell in a list is
53 @code{nil}. We call such a @code{nil}-terminated structure a
54 @dfn{true list}. In Emacs Lisp, the symbol @code{nil} is both a
55 symbol and a list with no elements. For convenience, the symbol
56 @code{nil} is considered to have @code{nil} as its @sc{cdr} (and also
59 Hence, the @sc{cdr} of a true list is always a true list. The
60 @sc{cdr} of a nonempty true list is a true list containing all the
61 elements except the first.
65 If the @sc{cdr} of a list's last cons cell is some value other than
66 @code{nil}, we call the structure a @dfn{dotted list}, since its
67 printed representation would use dotted pair notation (@pxref{Dotted
68 Pair Notation}). There is one other possibility: some cons cell's
69 @sc{cdr} could point to one of the previous cons cells in the list.
70 We call that structure a @dfn{circular list}.
72 For some purposes, it does not matter whether a list is true,
73 circular or dotted. If a program doesn't look far enough down the
74 list to see the @sc{cdr} of the final cons cell, it won't care.
75 However, some functions that operate on lists demand true lists and
76 signal errors if given a dotted list. Most functions that try to find
77 the end of a list enter infinite loops if given a circular list.
79 @cindex list structure
80 Because most cons cells are used as part of lists, we refer to any
81 structure made out of cons cells as a @dfn{list structure}.
83 @node List-related Predicates
84 @section Predicates on Lists
86 The following predicates test whether a Lisp object is an atom,
87 whether it is a cons cell or is a list, or whether it is the
88 distinguished object @code{nil}. (Many of these predicates can be
89 defined in terms of the others, but they are used so often that it is
93 This function returns @code{t} if @var{object} is a cons cell, @code{nil}
94 otherwise. @code{nil} is not a cons cell, although it @emph{is} a list.
98 This function returns @code{t} if @var{object} is an atom, @code{nil}
99 otherwise. All objects except cons cells are atoms. The symbol
100 @code{nil} is an atom and is also a list; it is the only Lisp object
104 (atom @var{object}) @equiv{} (not (consp @var{object}))
109 This function returns @code{t} if @var{object} is a cons cell or
110 @code{nil}. Otherwise, it returns @code{nil}.
125 This function is the opposite of @code{listp}: it returns @code{t} if
126 @var{object} is not a list. Otherwise, it returns @code{nil}.
129 (listp @var{object}) @equiv{} (not (nlistp @var{object}))
134 This function returns @code{t} if @var{object} is @code{nil}, and
135 returns @code{nil} otherwise. This function is identical to @code{not},
136 but as a matter of clarity we use @code{null} when @var{object} is
137 considered a list and @code{not} when it is considered a truth value
138 (see @code{not} in @ref{Combining Conditions}).
154 @section Accessing Elements of Lists
155 @cindex list elements
158 This function returns the value referred to by the first slot of the
159 cons cell @var{cons-cell}. In other words, it returns the @sc{car} of
162 As a special case, if @var{cons-cell} is @code{nil}, this function
163 returns @code{nil}. Therefore, any list is a valid argument. An
164 error is signaled if the argument is not a cons cell or @code{nil}.
179 This function returns the value referred to by the second slot of the
180 cons cell @var{cons-cell}. In other words, it returns the @sc{cdr} of
183 As a special case, if @var{cons-cell} is @code{nil}, this function
184 returns @code{nil}; therefore, any list is a valid argument. An error
185 is signaled if the argument is not a cons cell or @code{nil}.
199 @defun car-safe object
200 This function lets you take the @sc{car} of a cons cell while avoiding
201 errors for other data types. It returns the @sc{car} of @var{object} if
202 @var{object} is a cons cell, @code{nil} otherwise. This is in contrast
203 to @code{car}, which signals an error if @var{object} is not a list.
207 (car-safe @var{object})
209 (let ((x @var{object}))
217 @defun cdr-safe object
218 This function lets you take the @sc{cdr} of a cons cell while
219 avoiding errors for other data types. It returns the @sc{cdr} of
220 @var{object} if @var{object} is a cons cell, @code{nil} otherwise.
221 This is in contrast to @code{cdr}, which signals an error if
222 @var{object} is not a list.
226 (cdr-safe @var{object})
228 (let ((x @var{object}))
237 This macro is a way of examining the @sc{car} of a list,
238 and taking it off the list, all at once.
240 It operates on the list which is stored in the symbol @var{listname}.
241 It removes this element from the list by setting @var{listname}
242 to the @sc{cdr} of its old value---but it also returns the @sc{car}
243 of that list, which is the element being removed.
255 For the @code{pop} macro, which removes an element from a list,
256 @xref{List Variables}.
260 @anchor{Definition of nth}
261 This function returns the @var{n}th element of @var{list}. Elements
262 are numbered starting with zero, so the @sc{car} of @var{list} is
263 element number zero. If the length of @var{list} is @var{n} or less,
264 the value is @code{nil}.
266 If @var{n} is negative, @code{nth} returns the first element of
282 (nth n x) @equiv{} (car (nthcdr n x))
286 The function @code{elt} is similar, but applies to any kind of sequence.
287 For historical reasons, it takes its arguments in the opposite order.
288 @xref{Sequence Functions}.
292 This function returns the @var{n}th @sc{cdr} of @var{list}. In other
293 words, it skips past the first @var{n} links of @var{list} and returns
296 If @var{n} is zero or negative, @code{nthcdr} returns all of
297 @var{list}. If the length of @var{list} is @var{n} or less,
298 @code{nthcdr} returns @code{nil}.
302 (nthcdr 1 '(1 2 3 4))
306 (nthcdr 10 '(1 2 3 4))
310 (nthcdr -3 '(1 2 3 4))
316 @defun last list &optional n
317 This function returns the last link of @var{list}. The @code{car} of
318 this link is the list's last element. If @var{list} is null,
319 @code{nil} is returned. If @var{n} is non-@code{nil}, the
320 @var{n}th-to-last link is returned instead, or the whole of @var{list}
321 if @var{n} is bigger than @var{list}'s length.
324 @defun safe-length list
325 @anchor{Definition of safe-length}
326 This function returns the length of @var{list}, with no risk of either
327 an error or an infinite loop. It generally returns the number of
328 distinct cons cells in the list. However, for circular lists,
329 the value is just an upper bound; it is often too large.
331 If @var{list} is not @code{nil} or a cons cell, @code{safe-length}
335 The most common way to compute the length of a list, when you are not
336 worried that it may be circular, is with @code{length}. @xref{Sequence
339 @defun caar cons-cell
340 This is the same as @code{(car (car @var{cons-cell}))}.
343 @defun cadr cons-cell
344 This is the same as @code{(car (cdr @var{cons-cell}))}
345 or @code{(nth 1 @var{cons-cell})}.
348 @defun cdar cons-cell
349 This is the same as @code{(cdr (car @var{cons-cell}))}.
352 @defun cddr cons-cell
353 This is the same as @code{(cdr (cdr @var{cons-cell}))}
354 or @code{(nthcdr 2 @var{cons-cell})}.
357 @defun butlast x &optional n
358 This function returns the list @var{x} with the last element,
359 or the last @var{n} elements, removed. If @var{n} is greater
360 than zero it makes a copy of the list so as not to damage the
361 original list. In general, @code{(append (butlast @var{x} @var{n})
362 (last @var{x} @var{n}))} will return a list equal to @var{x}.
365 @defun nbutlast x &optional n
366 This is a version of @code{butlast} that works by destructively
367 modifying the @code{cdr} of the appropriate element, rather than
368 making a copy of the list.
372 @section Building Cons Cells and Lists
374 @cindex building lists
376 Many functions build lists, as lists reside at the very heart of Lisp.
377 @code{cons} is the fundamental list-building function; however, it is
378 interesting to note that @code{list} is used more times in the source
379 code for Emacs than @code{cons}.
381 @defun cons object1 object2
382 This function is the most basic function for building new list
383 structure. It creates a new cons cell, making @var{object1} the
384 @sc{car}, and @var{object2} the @sc{cdr}. It then returns the new
385 cons cell. The arguments @var{object1} and @var{object2} may be any
386 Lisp objects, but most often @var{object2} is a list.
404 @code{cons} is often used to add a single element to the front of a
405 list. This is called @dfn{consing the element onto the list}.
406 @footnote{There is no strictly equivalent way to add an element to
407 the end of a list. You can use @code{(append @var{listname} (list
408 @var{newelt}))}, which creates a whole new list by copying @var{listname}
409 and adding @var{newelt} to its end. Or you can use @code{(nconc
410 @var{listname} (list @var{newelt}))}, which modifies @var{listname}
411 by following all the @sc{cdr}s and then replacing the terminating
412 @code{nil}. Compare this to adding an element to the beginning of a
413 list with @code{cons}, which neither copies nor modifies the list.}
417 (setq list (cons newelt list))
420 Note that there is no conflict between the variable named @code{list}
421 used in this example and the function named @code{list} described below;
422 any symbol can serve both purposes.
425 @defun list &rest objects
426 This function creates a list with @var{objects} as its elements. The
427 resulting list is always @code{nil}-terminated. If no @var{objects}
428 are given, the empty list is returned.
433 @result{} (1 2 3 4 5)
436 (list 1 2 '(3 4 5) 'foo)
437 @result{} (1 2 (3 4 5) foo)
446 @defun make-list length object
447 This function creates a list of @var{length} elements, in which each
448 element is @var{object}. Compare @code{make-list} with
449 @code{make-string} (@pxref{Creating Strings}).
454 @result{} (pigs pigs pigs)
461 (setq l (make-list 3 '(a b)))
462 @result{} ((a b) (a b) (a b))
463 (eq (car l) (cadr l))
469 @defun append &rest sequences
470 @cindex copying lists
471 This function returns a list containing all the elements of
472 @var{sequences}. The @var{sequences} may be lists, vectors,
473 bool-vectors, or strings, but the last one should usually be a list.
474 All arguments except the last one are copied, so none of the arguments
475 is altered. (See @code{nconc} in @ref{Rearrangement}, for a way to join
476 lists with no copying.)
478 More generally, the final argument to @code{append} may be any Lisp
479 object. The final argument is not copied or converted; it becomes the
480 @sc{cdr} of the last cons cell in the new list. If the final argument
481 is itself a list, then its elements become in effect elements of the
482 result list. If the final element is not a list, the result is a
483 dotted list since its final @sc{cdr} is not @code{nil} as required
487 Here is an example of using @code{append}:
491 (setq trees '(pine oak))
493 (setq more-trees (append '(maple birch) trees))
494 @result{} (maple birch pine oak)
501 @result{} (maple birch pine oak)
504 (eq trees (cdr (cdr more-trees)))
509 You can see how @code{append} works by looking at a box diagram. The
510 variable @code{trees} is set to the list @code{(pine oak)} and then the
511 variable @code{more-trees} is set to the list @code{(maple birch pine
512 oak)}. However, the variable @code{trees} continues to refer to the
519 | --- --- --- --- -> --- --- --- ---
520 --> | | |--> | | |--> | | |--> | | |--> nil
521 --- --- --- --- --- --- --- ---
524 --> maple -->birch --> pine --> oak
528 An empty sequence contributes nothing to the value returned by
529 @code{append}. As a consequence of this, a final @code{nil} argument
530 forces a copy of the previous argument:
538 (setq wood (append trees nil))
552 This once was the usual way to copy a list, before the function
553 @code{copy-sequence} was invented. @xref{Sequences Arrays Vectors}.
555 Here we show the use of vectors and strings as arguments to @code{append}:
559 (append [a b] "cd" nil)
560 @result{} (a b 99 100)
564 With the help of @code{apply} (@pxref{Calling Functions}), we can append
565 all the lists in a list of lists:
569 (apply 'append '((a b c) nil (x y z) nil))
570 @result{} (a b c x y z)
574 If no @var{sequences} are given, @code{nil} is returned:
583 Here are some examples where the final argument is not a list:
589 @result{} (x y . [z])
593 The second example shows that when the final argument is a sequence but
594 not a list, the sequence's elements do not become elements of the
595 resulting list. Instead, the sequence becomes the final @sc{cdr}, like
596 any other non-list final argument.
599 This function creates a new list whose elements are the elements of
600 @var{list}, but in reverse order. The original argument @var{list} is
617 @defun copy-tree tree &optional vecp
618 This function returns a copy of the tree @code{tree}. If @var{tree} is a
619 cons cell, this makes a new cons cell with the same @sc{car} and
620 @sc{cdr}, then recursively copies the @sc{car} and @sc{cdr} in the
623 Normally, when @var{tree} is anything other than a cons cell,
624 @code{copy-tree} simply returns @var{tree}. However, if @var{vecp} is
625 non-@code{nil}, it copies vectors too (and operates recursively on
629 @defun number-sequence from &optional to separation
630 This returns a list of numbers starting with @var{from} and
631 incrementing by @var{separation}, and ending at or just before
632 @var{to}. @var{separation} can be positive or negative and defaults
633 to 1. If @var{to} is @code{nil} or numerically equal to @var{from},
634 the value is the one-element list @code{(@var{from})}. If @var{to} is
635 less than @var{from} with a positive @var{separation}, or greater than
636 @var{from} with a negative @var{separation}, the value is @code{nil}
637 because those arguments specify an empty sequence.
639 If @var{separation} is 0 and @var{to} is neither @code{nil} nor
640 numerically equal to @var{from}, @code{number-sequence} signals an
641 error, since those arguments specify an infinite sequence.
643 All arguments can be integers or floating point numbers. However,
644 floating point arguments can be tricky, because floating point
645 arithmetic is inexact. For instance, depending on the machine, it may
646 quite well happen that @code{(number-sequence 0.4 0.6 0.2)} returns
647 the one element list @code{(0.4)}, whereas
648 @code{(number-sequence 0.4 0.8 0.2)} returns a list with three
649 elements. The @var{n}th element of the list is computed by the exact
650 formula @code{(+ @var{from} (* @var{n} @var{separation}))}. Thus, if
651 one wants to make sure that @var{to} is included in the list, one can
652 pass an expression of this exact type for @var{to}. Alternatively,
653 one can replace @var{to} with a slightly larger value (or a slightly
654 more negative value if @var{separation} is negative).
659 (number-sequence 4 9)
660 @result{} (4 5 6 7 8 9)
661 (number-sequence 9 4 -1)
662 @result{} (9 8 7 6 5 4)
663 (number-sequence 9 4 -2)
667 (number-sequence 8 5)
669 (number-sequence 5 8 -1)
671 (number-sequence 1.5 6 2)
672 @result{} (1.5 3.5 5.5)
677 @section Modifying List Variables
679 These functions, and one macro, provide convenient ways
680 to modify a list which is stored in a variable.
682 @defmac push newelt listname
683 This macro provides an alternative way to write
684 @code{(setq @var{listname} (cons @var{newelt} @var{listname}))}.
696 For the @code{pop} macro, which removes the first element from a list,
697 @xref{List Elements}.
700 Two functions modify lists that are the values of variables.
702 @defun add-to-list symbol element &optional append compare-fn
703 This function sets the variable @var{symbol} by consing @var{element}
704 onto the old value, if @var{element} is not already a member of that
705 value. It returns the resulting list, whether updated or not. The
706 value of @var{symbol} had better be a list already before the call.
707 @code{add-to-list} uses @var{compare-fn} to compare @var{element}
708 against existing list members; if @var{compare-fn} is @code{nil}, it
711 Normally, if @var{element} is added, it is added to the front of
712 @var{symbol}, but if the optional argument @var{append} is
713 non-@code{nil}, it is added at the end.
715 The argument @var{symbol} is not implicitly quoted; @code{add-to-list}
716 is an ordinary function, like @code{set} and unlike @code{setq}. Quote
717 the argument yourself if that is what you want.
720 Here's a scenario showing how to use @code{add-to-list}:
726 (add-to-list 'foo 'c) ;; @r{Add @code{c}.}
729 (add-to-list 'foo 'b) ;; @r{No effect.}
732 foo ;; @r{@code{foo} was changed.}
736 An equivalent expression for @code{(add-to-list '@var{var}
737 @var{value})} is this:
740 (or (member @var{value} @var{var})
741 (setq @var{var} (cons @var{value} @var{var})))
744 @defun add-to-ordered-list symbol element &optional order
745 This function sets the variable @var{symbol} by inserting
746 @var{element} into the old value, which must be a list, at the
747 position specified by @var{order}. If @var{element} is already a
748 member of the list, its position in the list is adjusted according
749 to @var{order}. Membership is tested using @code{eq}.
750 This function returns the resulting list, whether updated or not.
752 The @var{order} is typically a number (integer or float), and the
753 elements of the list are sorted in non-decreasing numerical order.
755 @var{order} may also be omitted or @code{nil}. Then the numeric order
756 of @var{element} stays unchanged if it already has one; otherwise,
757 @var{element} has no numeric order. Elements without a numeric list
758 order are placed at the end of the list, in no particular order.
760 Any other value for @var{order} removes the numeric order of @var{element}
761 if it already has one; otherwise, it is equivalent to @code{nil}.
763 The argument @var{symbol} is not implicitly quoted;
764 @code{add-to-ordered-list} is an ordinary function, like @code{set}
765 and unlike @code{setq}. Quote the argument yourself if necessary.
767 The ordering information is stored in a hash table on @var{symbol}'s
768 @code{list-order} property.
771 Here's a scenario showing how to use @code{add-to-ordered-list}:
777 (add-to-ordered-list 'foo 'a 1) ;; @r{Add @code{a}.}
780 (add-to-ordered-list 'foo 'c 3) ;; @r{Add @code{c}.}
783 (add-to-ordered-list 'foo 'b 2) ;; @r{Add @code{b}.}
786 (add-to-ordered-list 'foo 'b 4) ;; @r{Move @code{b}.}
789 (add-to-ordered-list 'foo 'd) ;; @r{Append @code{d}.}
792 (add-to-ordered-list 'foo 'e) ;; @r{Add @code{e}}.
793 @result{} (a c b e d)
795 foo ;; @r{@code{foo} was changed.}
796 @result{} (a c b e d)
799 @node Modifying Lists
800 @section Modifying Existing List Structure
801 @cindex destructive list operations
803 You can modify the @sc{car} and @sc{cdr} contents of a cons cell with the
804 primitives @code{setcar} and @code{setcdr}. We call these ``destructive''
805 operations because they change existing list structure.
807 @cindex CL note---@code{rplaca} vs @code{setcar}
811 @b{Common Lisp note:} Common Lisp uses functions @code{rplaca} and
812 @code{rplacd} to alter list structure; they change structure the same
813 way as @code{setcar} and @code{setcdr}, but the Common Lisp functions
814 return the cons cell while @code{setcar} and @code{setcdr} return the
815 new @sc{car} or @sc{cdr}.
819 * Setcar:: Replacing an element in a list.
820 * Setcdr:: Replacing part of the list backbone.
821 This can be used to remove or add elements.
822 * Rearrangement:: Reordering the elements in a list; combining lists.
826 @subsection Altering List Elements with @code{setcar}
828 Changing the @sc{car} of a cons cell is done with @code{setcar}. When
829 used on a list, @code{setcar} replaces one element of a list with a
832 @defun setcar cons object
833 This function stores @var{object} as the new @sc{car} of @var{cons},
834 replacing its previous @sc{car}. In other words, it changes the
835 @sc{car} slot of @var{cons} to refer to @var{object}. It returns the
836 value @var{object}. For example:
854 When a cons cell is part of the shared structure of several lists,
855 storing a new @sc{car} into the cons changes one element of each of
856 these lists. Here is an example:
860 ;; @r{Create two lists that are partly shared.}
863 (setq x2 (cons 'z (cdr x1)))
868 ;; @r{Replace the @sc{car} of a shared link.}
869 (setcar (cdr x1) 'foo)
871 x1 ; @r{Both lists are changed.}
878 ;; @r{Replace the @sc{car} of a link that is not shared.}
881 x1 ; @r{Only one list is changed.}
882 @result{} (baz foo c)
888 Here is a graphical depiction of the shared structure of the two lists
889 in the variables @code{x1} and @code{x2}, showing why replacing @code{b}
894 --- --- --- --- --- ---
895 x1---> | | |----> | | |--> | | |--> nil
896 --- --- --- --- --- ---
910 Here is an alternative form of box diagram, showing the same relationship:
915 -------------- -------------- --------------
916 | car | cdr | | car | cdr | | car | cdr |
917 | a | o------->| b | o------->| c | nil |
919 -------------- | -------------- --------------
931 @subsection Altering the CDR of a List
933 The lowest-level primitive for modifying a @sc{cdr} is @code{setcdr}:
935 @defun setcdr cons object
936 This function stores @var{object} as the new @sc{cdr} of @var{cons},
937 replacing its previous @sc{cdr}. In other words, it changes the
938 @sc{cdr} slot of @var{cons} to refer to @var{object}. It returns the
942 Here is an example of replacing the @sc{cdr} of a list with a
943 different list. All but the first element of the list are removed in
944 favor of a different sequence of elements. The first element is
945 unchanged, because it resides in the @sc{car} of the list, and is not
946 reached via the @sc{cdr}.
963 You can delete elements from the middle of a list by altering the
964 @sc{cdr}s of the cons cells in the list. For example, here we delete
965 the second element, @code{b}, from the list @code{(a b c)}, by changing
966 the @sc{cdr} of the first cons cell:
972 (setcdr x1 (cdr (cdr x1)))
979 Here is the result in box notation:
985 -------------- | -------------- | --------------
986 | car | cdr | | | car | cdr | -->| car | cdr |
987 | a | o----- | b | o-------->| c | nil |
989 -------------- -------------- --------------
994 The second cons cell, which previously held the element @code{b}, still
995 exists and its @sc{car} is still @code{b}, but it no longer forms part
998 It is equally easy to insert a new element by changing @sc{cdr}s:
1004 (setcdr x1 (cons 'd (cdr x1)))
1011 Here is this result in box notation:
1015 -------------- ------------- -------------
1016 | car | cdr | | car | cdr | | car | cdr |
1017 | a | o | -->| b | o------->| c | nil |
1018 | | | | | | | | | | |
1019 --------- | -- | ------------- -------------
1032 @subsection Functions that Rearrange Lists
1033 @cindex rearrangement of lists
1034 @cindex modification of lists
1036 Here are some functions that rearrange lists ``destructively'' by
1037 modifying the @sc{cdr}s of their component cons cells. We call these
1038 functions ``destructive'' because they chew up the original lists passed
1039 to them as arguments, relinking their cons cells to form a new list that
1040 is the returned value.
1043 See @code{delq}, in @ref{Sets And Lists}, for another function
1044 that modifies cons cells.
1047 The function @code{delq} in the following section is another example
1048 of destructive list manipulation.
1051 @defun nconc &rest lists
1052 @cindex concatenating lists
1053 @cindex joining lists
1054 This function returns a list containing all the elements of @var{lists}.
1055 Unlike @code{append} (@pxref{Building Lists}), the @var{lists} are
1056 @emph{not} copied. Instead, the last @sc{cdr} of each of the
1057 @var{lists} is changed to refer to the following list. The last of the
1058 @var{lists} is not altered. For example:
1067 @result{} (1 2 3 4 5)
1071 @result{} (1 2 3 4 5)
1075 Since the last argument of @code{nconc} is not itself modified, it is
1076 reasonable to use a constant list, such as @code{'(4 5)}, as in the
1077 above example. For the same reason, the last argument need not be a
1087 @result{} (1 2 3 . z)
1091 @result{} (1 2 3 . z)
1095 However, the other arguments (all but the last) must be lists.
1097 A common pitfall is to use a quoted constant list as a non-last
1098 argument to @code{nconc}. If you do this, your program will change
1099 each time you run it! Here is what happens:
1103 (defun add-foo (x) ; @r{We want this function to add}
1104 (nconc '(foo) x)) ; @r{@code{foo} to the front of its arg.}
1108 (symbol-function 'add-foo)
1109 @result{} (lambda (x) (nconc (quote (foo)) x))
1113 (setq xx (add-foo '(1 2))) ; @r{It seems to work.}
1117 (setq xy (add-foo '(3 4))) ; @r{What happened?}
1118 @result{} (foo 1 2 3 4)
1126 (symbol-function 'add-foo)
1127 @result{} (lambda (x) (nconc (quote (foo 1 2 3 4) x)))
1132 @defun nreverse list
1133 @cindex reversing a list
1134 This function reverses the order of the elements of @var{list}.
1135 Unlike @code{reverse}, @code{nreverse} alters its argument by reversing
1136 the @sc{cdr}s in the cons cells forming the list. The cons cell that
1137 used to be the last one in @var{list} becomes the first cons cell of the
1154 ;; @r{The cons cell that was first is now last.}
1160 To avoid confusion, we usually store the result of @code{nreverse}
1161 back in the same variable which held the original list:
1164 (setq x (nreverse x))
1167 Here is the @code{nreverse} of our favorite example, @code{(a b c)},
1168 presented graphically:
1172 @r{Original list head:} @r{Reversed list:}
1173 ------------- ------------- ------------
1174 | car | cdr | | car | cdr | | car | cdr |
1175 | a | nil |<-- | b | o |<-- | c | o |
1176 | | | | | | | | | | | | |
1177 ------------- | --------- | - | -------- | -
1179 ------------- ------------
1184 @defun sort list predicate
1186 @cindex sorting lists
1187 This function sorts @var{list} stably, though destructively, and
1188 returns the sorted list. It compares elements using @var{predicate}. A
1189 stable sort is one in which elements with equal sort keys maintain their
1190 relative order before and after the sort. Stability is important when
1191 successive sorts are used to order elements according to different
1194 The argument @var{predicate} must be a function that accepts two
1195 arguments. It is called with two elements of @var{list}. To get an
1196 increasing order sort, the @var{predicate} should return non-@code{nil} if the
1197 first element is ``less than'' the second, or @code{nil} if not.
1199 The comparison function @var{predicate} must give reliable results for
1200 any given pair of arguments, at least within a single call to
1201 @code{sort}. It must be @dfn{antisymmetric}; that is, if @var{a} is
1202 less than @var{b}, @var{b} must not be less than @var{a}. It must be
1203 @dfn{transitive}---that is, if @var{a} is less than @var{b}, and @var{b}
1204 is less than @var{c}, then @var{a} must be less than @var{c}. If you
1205 use a comparison function which does not meet these requirements, the
1206 result of @code{sort} is unpredictable.
1208 The destructive aspect of @code{sort} is that it rearranges the cons
1209 cells forming @var{list} by changing @sc{cdr}s. A nondestructive sort
1210 function would create new cons cells to store the elements in their
1211 sorted order. If you wish to make a sorted copy without destroying the
1212 original, copy it first with @code{copy-sequence} and then sort.
1214 Sorting does not change the @sc{car}s of the cons cells in @var{list};
1215 the cons cell that originally contained the element @code{a} in
1216 @var{list} still has @code{a} in its @sc{car} after sorting, but it now
1217 appears in a different position in the list due to the change of
1218 @sc{cdr}s. For example:
1222 (setq nums '(1 3 2 6 5 4 0))
1223 @result{} (1 3 2 6 5 4 0)
1227 @result{} (0 1 2 3 4 5 6)
1231 @result{} (1 2 3 4 5 6)
1236 @strong{Warning}: Note that the list in @code{nums} no longer contains
1237 0; this is the same cons cell that it was before, but it is no longer
1238 the first one in the list. Don't assume a variable that formerly held
1239 the argument now holds the entire sorted list! Instead, save the result
1240 of @code{sort} and use that. Most often we store the result back into
1241 the variable that held the original list:
1244 (setq nums (sort nums '<))
1247 @xref{Sorting}, for more functions that perform sorting.
1248 See @code{documentation} in @ref{Accessing Documentation}, for a
1249 useful example of @code{sort}.
1252 @node Sets And Lists
1253 @section Using Lists as Sets
1254 @cindex lists as sets
1257 A list can represent an unordered mathematical set---simply consider a
1258 value an element of a set if it appears in the list, and ignore the
1259 order of the list. To form the union of two sets, use @code{append} (as
1260 long as you don't mind having duplicate elements). You can remove
1261 @code{equal} duplicates using @code{delete-dups}. Other useful
1262 functions for sets include @code{memq} and @code{delq}, and their
1263 @code{equal} versions, @code{member} and @code{delete}.
1265 @cindex CL note---lack @code{union}, @code{intersection}
1267 @b{Common Lisp note:} Common Lisp has functions @code{union} (which
1268 avoids duplicate elements) and @code{intersection} for set operations.
1269 Although standard GNU Emacs Lisp does not have them, the @file{cl}
1270 library provides versions. @xref{Top,, Overview, cl, Common Lisp Extensions}.
1273 @defun memq object list
1274 @cindex membership in a list
1275 This function tests to see whether @var{object} is a member of
1276 @var{list}. If it is, @code{memq} returns a list starting with the
1277 first occurrence of @var{object}. Otherwise, it returns @code{nil}.
1278 The letter @samp{q} in @code{memq} says that it uses @code{eq} to
1279 compare @var{object} against the elements of the list. For example:
1283 (memq 'b '(a b c b a))
1287 (memq '(2) '((1) (2))) ; @r{@code{(2)} and @code{(2)} are not @code{eq}.}
1293 @defun delq object list
1294 @cindex deleting list elements
1295 This function destructively removes all elements @code{eq} to
1296 @var{object} from @var{list}. The letter @samp{q} in @code{delq} says
1297 that it uses @code{eq} to compare @var{object} against the elements of
1298 the list, like @code{memq} and @code{remq}.
1301 When @code{delq} deletes elements from the front of the list, it does so
1302 simply by advancing down the list and returning a sublist that starts
1303 after those elements:
1307 (delq 'a '(a b c)) @equiv{} (cdr '(a b c))
1311 When an element to be deleted appears in the middle of the list,
1312 removing it involves changing the @sc{cdr}s (@pxref{Setcdr}).
1316 (setq sample-list '(a b c (4)))
1317 @result{} (a b c (4))
1320 (delq 'a sample-list)
1325 @result{} (a b c (4))
1328 (delq 'c sample-list)
1337 Note that @code{(delq 'c sample-list)} modifies @code{sample-list} to
1338 splice out the third element, but @code{(delq 'a sample-list)} does not
1339 splice anything---it just returns a shorter list. Don't assume that a
1340 variable which formerly held the argument @var{list} now has fewer
1341 elements, or that it still holds the original list! Instead, save the
1342 result of @code{delq} and use that. Most often we store the result back
1343 into the variable that held the original list:
1346 (setq flowers (delq 'rose flowers))
1349 In the following example, the @code{(4)} that @code{delq} attempts to match
1350 and the @code{(4)} in the @code{sample-list} are not @code{eq}:
1354 (delq '(4) sample-list)
1359 If you want to delete elements that are @code{equal} to a given value,
1360 use @code{delete} (see below).
1362 @defun remq object list
1363 This function returns a copy of @var{list}, with all elements removed
1364 which are @code{eq} to @var{object}. The letter @samp{q} in @code{remq}
1365 says that it uses @code{eq} to compare @var{object} against the elements
1370 (setq sample-list '(a b c a b c))
1371 @result{} (a b c a b c)
1374 (remq 'a sample-list)
1379 @result{} (a b c a b c)
1384 @defun memql object list
1385 The function @code{memql} tests to see whether @var{object} is a member
1386 of @var{list}, comparing members with @var{object} using @code{eql},
1387 so floating point elements are compared by value.
1388 If @var{object} is a member, @code{memql} returns a list starting with
1389 its first occurrence in @var{list}. Otherwise, it returns @code{nil}.
1391 Compare this with @code{memq}:
1395 (memql 1.2 '(1.1 1.2 1.3)) ; @r{@code{1.2} and @code{1.2} are @code{eql}.}
1399 (memq 1.2 '(1.1 1.2 1.3)) ; @r{@code{1.2} and @code{1.2} are not @code{eq}.}
1405 The following three functions are like @code{memq}, @code{delq} and
1406 @code{remq}, but use @code{equal} rather than @code{eq} to compare
1407 elements. @xref{Equality Predicates}.
1409 @defun member object list
1410 The function @code{member} tests to see whether @var{object} is a member
1411 of @var{list}, comparing members with @var{object} using @code{equal}.
1412 If @var{object} is a member, @code{member} returns a list starting with
1413 its first occurrence in @var{list}. Otherwise, it returns @code{nil}.
1415 Compare this with @code{memq}:
1419 (member '(2) '((1) (2))) ; @r{@code{(2)} and @code{(2)} are @code{equal}.}
1423 (memq '(2) '((1) (2))) ; @r{@code{(2)} and @code{(2)} are not @code{eq}.}
1427 ;; @r{Two strings with the same contents are @code{equal}.}
1428 (member "foo" '("foo" "bar"))
1429 @result{} ("foo" "bar")
1434 @defun delete object sequence
1435 If @code{sequence} is a list, this function destructively removes all
1436 elements @code{equal} to @var{object} from @var{sequence}. For lists,
1437 @code{delete} is to @code{delq} as @code{member} is to @code{memq}: it
1438 uses @code{equal} to compare elements with @var{object}, like
1439 @code{member}; when it finds an element that matches, it cuts the
1440 element out just as @code{delq} would.
1442 If @code{sequence} is a vector or string, @code{delete} returns a copy
1443 of @code{sequence} with all elements @code{equal} to @code{object}
1450 (setq l '((2) (1) (2)))
1455 ;; @r{If you want to change @code{l} reliably,}
1456 ;; @r{write @code{(setq l (delete '(2) l))}.}
1459 (setq l '((2) (1) (2)))
1464 ;; @r{In this case, it makes no difference whether you set @code{l},}
1465 ;; @r{but you should do so for the sake of the other case.}
1468 (delete '(2) [(2) (1) (2)])
1474 @defun remove object sequence
1475 This function is the non-destructive counterpart of @code{delete}. It
1476 returns a copy of @code{sequence}, a list, vector, or string, with
1477 elements @code{equal} to @code{object} removed. For example:
1481 (remove '(2) '((2) (1) (2)))
1485 (remove '(2) [(2) (1) (2)])
1492 @b{Common Lisp note:} The functions @code{member}, @code{delete} and
1493 @code{remove} in GNU Emacs Lisp are derived from Maclisp, not Common
1494 Lisp. The Common Lisp versions do not use @code{equal} to compare
1498 @defun member-ignore-case object list
1499 This function is like @code{member}, except that @var{object} should
1500 be a string and that it ignores differences in letter-case and text
1501 representation: upper-case and lower-case letters are treated as
1502 equal, and unibyte strings are converted to multibyte prior to
1506 @defun delete-dups list
1507 This function destructively removes all @code{equal} duplicates from
1508 @var{list}, stores the result in @var{list} and returns it. Of
1509 several @code{equal} occurrences of an element in @var{list},
1510 @code{delete-dups} keeps the first one.
1513 See also the function @code{add-to-list}, in @ref{List Variables},
1514 for a way to add an element to a list stored in a variable and used as a
1517 @node Association Lists
1518 @section Association Lists
1519 @cindex association list
1522 An @dfn{association list}, or @dfn{alist} for short, records a mapping
1523 from keys to values. It is a list of cons cells called
1524 @dfn{associations}: the @sc{car} of each cons cell is the @dfn{key}, and the
1525 @sc{cdr} is the @dfn{associated value}.@footnote{This usage of ``key''
1526 is not related to the term ``key sequence''; it means a value used to
1527 look up an item in a table. In this case, the table is the alist, and
1528 the alist associations are the items.}
1530 Here is an example of an alist. The key @code{pine} is associated with
1531 the value @code{cones}; the key @code{oak} is associated with
1532 @code{acorns}; and the key @code{maple} is associated with @code{seeds}.
1542 Both the values and the keys in an alist may be any Lisp objects.
1543 For example, in the following alist, the symbol @code{a} is
1544 associated with the number @code{1}, and the string @code{"b"} is
1545 associated with the @emph{list} @code{(2 3)}, which is the @sc{cdr} of
1552 Sometimes it is better to design an alist to store the associated
1553 value in the @sc{car} of the @sc{cdr} of the element. Here is an
1554 example of such an alist:
1557 ((rose red) (lily white) (buttercup yellow))
1561 Here we regard @code{red} as the value associated with @code{rose}. One
1562 advantage of this kind of alist is that you can store other related
1563 information---even a list of other items---in the @sc{cdr} of the
1564 @sc{cdr}. One disadvantage is that you cannot use @code{rassq} (see
1565 below) to find the element containing a given value. When neither of
1566 these considerations is important, the choice is a matter of taste, as
1567 long as you are consistent about it for any given alist.
1569 The same alist shown above could be regarded as having the
1570 associated value in the @sc{cdr} of the element; the value associated
1571 with @code{rose} would be the list @code{(red)}.
1573 Association lists are often used to record information that you might
1574 otherwise keep on a stack, since new associations may be added easily to
1575 the front of the list. When searching an association list for an
1576 association with a given key, the first one found is returned, if there
1579 In Emacs Lisp, it is @emph{not} an error if an element of an
1580 association list is not a cons cell. The alist search functions simply
1581 ignore such elements. Many other versions of Lisp signal errors in such
1584 Note that property lists are similar to association lists in several
1585 respects. A property list behaves like an association list in which
1586 each key can occur only once. @xref{Property Lists}, for a comparison
1587 of property lists and association lists.
1589 @defun assoc key alist
1590 This function returns the first association for @var{key} in
1591 @var{alist}, comparing @var{key} against the alist elements using
1592 @code{equal} (@pxref{Equality Predicates}). It returns @code{nil} if no
1593 association in @var{alist} has a @sc{car} @code{equal} to @var{key}.
1597 (setq trees '((pine . cones) (oak . acorns) (maple . seeds)))
1598 @result{} ((pine . cones) (oak . acorns) (maple . seeds))
1600 @result{} (oak . acorns)
1601 (cdr (assoc 'oak trees))
1603 (assoc 'birch trees)
1607 Here is another example, in which the keys and values are not symbols:
1610 (setq needles-per-cluster
1611 '((2 "Austrian Pine" "Red Pine")
1615 (cdr (assoc 3 needles-per-cluster))
1616 @result{} ("Pitch Pine")
1617 (cdr (assoc 2 needles-per-cluster))
1618 @result{} ("Austrian Pine" "Red Pine")
1622 The function @code{assoc-string} is much like @code{assoc} except
1623 that it ignores certain differences between strings. @xref{Text
1626 @defun rassoc value alist
1627 This function returns the first association with value @var{value} in
1628 @var{alist}. It returns @code{nil} if no association in @var{alist} has
1629 a @sc{cdr} @code{equal} to @var{value}.
1631 @code{rassoc} is like @code{assoc} except that it compares the @sc{cdr} of
1632 each @var{alist} association instead of the @sc{car}. You can think of
1633 this as ``reverse @code{assoc}'', finding the key for a given value.
1636 @defun assq key alist
1637 This function is like @code{assoc} in that it returns the first
1638 association for @var{key} in @var{alist}, but it makes the comparison
1639 using @code{eq} instead of @code{equal}. @code{assq} returns @code{nil}
1640 if no association in @var{alist} has a @sc{car} @code{eq} to @var{key}.
1641 This function is used more often than @code{assoc}, since @code{eq} is
1642 faster than @code{equal} and most alists use symbols as keys.
1643 @xref{Equality Predicates}.
1646 (setq trees '((pine . cones) (oak . acorns) (maple . seeds)))
1647 @result{} ((pine . cones) (oak . acorns) (maple . seeds))
1649 @result{} (pine . cones)
1652 On the other hand, @code{assq} is not usually useful in alists where the
1653 keys may not be symbols:
1657 '(("simple leaves" . oak)
1658 ("compound leaves" . horsechestnut)))
1660 (assq "simple leaves" leaves)
1662 (assoc "simple leaves" leaves)
1663 @result{} ("simple leaves" . oak)
1667 @defun rassq value alist
1668 This function returns the first association with value @var{value} in
1669 @var{alist}. It returns @code{nil} if no association in @var{alist} has
1670 a @sc{cdr} @code{eq} to @var{value}.
1672 @code{rassq} is like @code{assq} except that it compares the @sc{cdr} of
1673 each @var{alist} association instead of the @sc{car}. You can think of
1674 this as ``reverse @code{assq}'', finding the key for a given value.
1679 (setq trees '((pine . cones) (oak . acorns) (maple . seeds)))
1681 (rassq 'acorns trees)
1682 @result{} (oak . acorns)
1683 (rassq 'spores trees)
1687 @code{rassq} cannot search for a value stored in the @sc{car}
1688 of the @sc{cdr} of an element:
1691 (setq colors '((rose red) (lily white) (buttercup yellow)))
1693 (rassq 'white colors)
1697 In this case, the @sc{cdr} of the association @code{(lily white)} is not
1698 the symbol @code{white}, but rather the list @code{(white)}. This
1699 becomes clearer if the association is written in dotted pair notation:
1702 (lily white) @equiv{} (lily . (white))
1706 @defun assoc-default key alist &optional test default
1707 This function searches @var{alist} for a match for @var{key}. For each
1708 element of @var{alist}, it compares the element (if it is an atom) or
1709 the element's @sc{car} (if it is a cons) against @var{key}, by calling
1710 @var{test} with two arguments: the element or its @sc{car}, and
1711 @var{key}. The arguments are passed in that order so that you can get
1712 useful results using @code{string-match} with an alist that contains
1713 regular expressions (@pxref{Regexp Search}). If @var{test} is omitted
1714 or @code{nil}, @code{equal} is used for comparison.
1716 If an alist element matches @var{key} by this criterion,
1717 then @code{assoc-default} returns a value based on this element.
1718 If the element is a cons, then the value is the element's @sc{cdr}.
1719 Otherwise, the return value is @var{default}.
1721 If no alist element matches @var{key}, @code{assoc-default} returns
1725 @defun copy-alist alist
1726 @cindex copying alists
1727 This function returns a two-level deep copy of @var{alist}: it creates a
1728 new copy of each association, so that you can alter the associations of
1729 the new alist without changing the old one.
1733 (setq needles-per-cluster
1734 '((2 . ("Austrian Pine" "Red Pine"))
1735 (3 . ("Pitch Pine"))
1737 (5 . ("White Pine"))))
1739 ((2 "Austrian Pine" "Red Pine")
1743 (setq copy (copy-alist needles-per-cluster))
1745 ((2 "Austrian Pine" "Red Pine")
1749 (eq needles-per-cluster copy)
1751 (equal needles-per-cluster copy)
1753 (eq (car needles-per-cluster) (car copy))
1755 (cdr (car (cdr needles-per-cluster)))
1756 @result{} ("Pitch Pine")
1758 (eq (cdr (car (cdr needles-per-cluster)))
1759 (cdr (car (cdr copy))))
1764 This example shows how @code{copy-alist} makes it possible to change
1765 the associations of one copy without affecting the other:
1769 (setcdr (assq 3 copy) '("Martian Vacuum Pine"))
1770 (cdr (assq 3 needles-per-cluster))
1771 @result{} ("Pitch Pine")
1776 @defun assq-delete-all key alist
1777 This function deletes from @var{alist} all the elements whose @sc{car}
1778 is @code{eq} to @var{key}, much as if you used @code{delq} to delete
1779 each such element one by one. It returns the shortened alist, and
1780 often modifies the original list structure of @var{alist}. For
1781 correct results, use the return value of @code{assq-delete-all} rather
1782 than looking at the saved value of @var{alist}.
1785 (setq alist '((foo 1) (bar 2) (foo 3) (lose 4)))
1786 @result{} ((foo 1) (bar 2) (foo 3) (lose 4))
1787 (assq-delete-all 'foo alist)
1788 @result{} ((bar 2) (lose 4))
1790 @result{} ((foo 1) (bar 2) (lose 4))
1794 @defun rassq-delete-all value alist
1795 This function deletes from @var{alist} all the elements whose @sc{cdr}
1796 is @code{eq} to @var{value}. It returns the shortened alist, and
1797 often modifies the original list structure of @var{alist}.
1798 @code{rassq-delete-all} is like @code{assq-delete-all} except that it
1799 compares the @sc{cdr} of each @var{alist} association instead of the