2 @c This is part of the GNU Emacs Lisp Reference Manual.
3 @c Copyright (C) 1990-1994, 1998-1999, 2001-2012 Free Software Foundation, Inc.
4 @c See the file elisp.texi for copying conditions.
6 @chapter Reading and Printing Lisp Objects
8 @dfn{Printing} and @dfn{reading} are the operations of converting Lisp
9 objects to textual form and vice versa. They use the printed
10 representations and read syntax described in @ref{Lisp Data Types}.
12 This chapter describes the Lisp functions for reading and printing.
13 It also describes @dfn{streams}, which specify where to get the text (if
14 reading) or where to put it (if printing).
17 * Streams Intro:: Overview of streams, reading and printing.
18 * Input Streams:: Various data types that can be used as input streams.
19 * Input Functions:: Functions to read Lisp objects from text.
20 * Output Streams:: Various data types that can be used as output streams.
21 * Output Functions:: Functions to print Lisp objects as text.
22 * Output Variables:: Variables that control what the printing functions do.
26 @section Introduction to Reading and Printing
31 @dfn{Reading} a Lisp object means parsing a Lisp expression in textual
32 form and producing a corresponding Lisp object. This is how Lisp
33 programs get into Lisp from files of Lisp code. We call the text the
34 @dfn{read syntax} of the object. For example, the text @samp{(a .@: 5)}
35 is the read syntax for a cons cell whose @sc{car} is @code{a} and whose
36 @sc{cdr} is the number 5.
38 @dfn{Printing} a Lisp object means producing text that represents that
39 object---converting the object to its @dfn{printed representation}
40 (@pxref{Printed Representation}). Printing the cons cell described
41 above produces the text @samp{(a .@: 5)}.
43 Reading and printing are more or less inverse operations: printing the
44 object that results from reading a given piece of text often produces
45 the same text, and reading the text that results from printing an object
46 usually produces a similar-looking object. For example, printing the
47 symbol @code{foo} produces the text @samp{foo}, and reading that text
48 returns the symbol @code{foo}. Printing a list whose elements are
49 @code{a} and @code{b} produces the text @samp{(a b)}, and reading that
50 text produces a list (but not the same list) with elements @code{a}
53 However, these two operations are not precisely inverse to each other.
54 There are three kinds of exceptions:
58 Printing can produce text that cannot be read. For example, buffers,
59 windows, frames, subprocesses and markers print as text that starts
60 with @samp{#}; if you try to read this text, you get an error. There is
61 no way to read those data types.
64 One object can have multiple textual representations. For example,
65 @samp{1} and @samp{01} represent the same integer, and @samp{(a b)} and
66 @samp{(a .@: (b))} represent the same list. Reading will accept any of
67 the alternatives, but printing must choose one of them.
70 Comments can appear at certain points in the middle of an object's
71 read sequence without affecting the result of reading it.
75 @section Input Streams
76 @cindex stream (for reading)
79 Most of the Lisp functions for reading text take an @dfn{input stream}
80 as an argument. The input stream specifies where or how to get the
81 characters of the text to be read. Here are the possible types of input
86 @cindex buffer input stream
87 The input characters are read from @var{buffer}, starting with the
88 character directly after point. Point advances as characters are read.
91 @cindex marker input stream
92 The input characters are read from the buffer that @var{marker} is in,
93 starting with the character directly after the marker. The marker
94 position advances as characters are read. The value of point in the
95 buffer has no effect when the stream is a marker.
98 @cindex string input stream
99 The input characters are taken from @var{string}, starting at the first
100 character in the string and using as many characters as required.
103 @cindex function input stream
104 The input characters are generated by @var{function}, which must support
109 When it is called with no arguments, it should return the next character.
112 When it is called with one argument (always a character), @var{function}
113 should save the argument and arrange to return it on the next call.
114 This is called @dfn{unreading} the character; it happens when the Lisp
115 reader reads one character too many and wants to ``put it back where it
116 came from''. In this case, it makes no difference what value
117 @var{function} returns.
121 @cindex @code{t} input stream
122 @code{t} used as a stream means that the input is read from the
123 minibuffer. In fact, the minibuffer is invoked once and the text
124 given by the user is made into a string that is then used as the
125 input stream. If Emacs is running in batch mode, standard input is used
126 instead of the minibuffer. For example,
128 (message "%s" (read t))
130 will read a Lisp expression from standard input and print the result
134 @cindex @code{nil} input stream
135 @code{nil} supplied as an input stream means to use the value of
136 @code{standard-input} instead; that value is the @dfn{default input
137 stream}, and must be a non-@code{nil} input stream.
140 A symbol as input stream is equivalent to the symbol's function
144 Here is an example of reading from a stream that is a buffer, showing
145 where point is located before and after:
149 ---------- Buffer: foo ----------
150 This@point{} is the contents of foo.
151 ---------- Buffer: foo ----------
155 (read (get-buffer "foo"))
159 (read (get-buffer "foo"))
164 ---------- Buffer: foo ----------
165 This is the@point{} contents of foo.
166 ---------- Buffer: foo ----------
171 Note that the first read skips a space. Reading skips any amount of
172 whitespace preceding the significant text.
174 Here is an example of reading from a stream that is a marker,
175 initially positioned at the beginning of the buffer shown. The value
176 read is the symbol @code{This}.
181 ---------- Buffer: foo ----------
182 This is the contents of foo.
183 ---------- Buffer: foo ----------
187 (setq m (set-marker (make-marker) 1 (get-buffer "foo")))
188 @result{} #<marker at 1 in foo>
196 @result{} #<marker at 5 in foo> ;; @r{Before the first space.}
200 Here we read from the contents of a string:
204 (read "(When in) the course")
209 The following example reads from the minibuffer. The
210 prompt is: @w{@samp{Lisp expression: }}. (That is always the prompt
211 used when you read from the stream @code{t}.) The user's input is shown
212 following the prompt.
218 ---------- Buffer: Minibuffer ----------
219 Lisp expression: @kbd{23 @key{RET}}
220 ---------- Buffer: Minibuffer ----------
224 Finally, here is an example of a stream that is a function, named
225 @code{useless-stream}. Before we use the stream, we initialize the
226 variable @code{useless-list} to a list of characters. Then each call to
227 the function @code{useless-stream} obtains the next character in the list
228 or unreads a character by adding it to the front of the list.
232 (setq useless-list (append "XY()" nil))
233 @result{} (88 89 40 41)
237 (defun useless-stream (&optional unread)
239 (setq useless-list (cons unread useless-list))
240 (prog1 (car useless-list)
241 (setq useless-list (cdr useless-list)))))
242 @result{} useless-stream
247 Now we read using the stream thus constructed:
251 (read 'useless-stream)
262 Note that the open and close parentheses remain in the list. The Lisp
263 reader encountered the open parenthesis, decided that it ended the
264 input, and unread it. Another attempt to read from the stream at this
265 point would read @samp{()} and return @code{nil}.
267 @node Input Functions
268 @section Input Functions
270 This section describes the Lisp functions and variables that pertain
273 In the functions below, @var{stream} stands for an input stream (see
274 the previous section). If @var{stream} is @code{nil} or omitted, it
275 defaults to the value of @code{standard-input}.
278 An @code{end-of-file} error is signaled if reading encounters an
279 unterminated list, vector, or string.
281 @defun read &optional stream
282 This function reads one textual Lisp expression from @var{stream},
283 returning it as a Lisp object. This is the basic Lisp input function.
286 @defun read-from-string string &optional start end
287 @cindex string to object
288 This function reads the first textual Lisp expression from the text in
289 @var{string}. It returns a cons cell whose @sc{car} is that expression,
290 and whose @sc{cdr} is an integer giving the position of the next
291 remaining character in the string (i.e., the first one not read).
293 If @var{start} is supplied, then reading begins at index @var{start} in
294 the string (where the first character is at index 0). If you specify
295 @var{end}, then reading is forced to stop just before that index, as if
296 the rest of the string were not there.
302 (read-from-string "(setq x 55) (setq y 5)")
303 @result{} ((setq x 55) . 11)
306 (read-from-string "\"A short string\"")
307 @result{} ("A short string" . 16)
311 ;; @r{Read starting at the first character.}
312 (read-from-string "(list 112)" 0)
313 @result{} ((list 112) . 10)
316 ;; @r{Read starting at the second character.}
317 (read-from-string "(list 112)" 1)
321 ;; @r{Read starting at the seventh character,}
322 ;; @r{and stopping at the ninth.}
323 (read-from-string "(list 112)" 6 8)
329 @defvar standard-input
330 This variable holds the default input stream---the stream that
331 @code{read} uses when the @var{stream} argument is @code{nil}.
332 The default is @code{t}, meaning use the minibuffer.
336 If non-@code{nil}, this variable enables the reading of circular and
337 shared structures. @xref{Circular Objects}. Its default value is
342 @section Output Streams
343 @cindex stream (for printing)
344 @cindex output stream
346 An output stream specifies what to do with the characters produced
347 by printing. Most print functions accept an output stream as an
348 optional argument. Here are the possible types of output stream:
352 @cindex buffer output stream
353 The output characters are inserted into @var{buffer} at point.
354 Point advances as characters are inserted.
357 @cindex marker output stream
358 The output characters are inserted into the buffer that @var{marker}
359 points into, at the marker position. The marker position advances as
360 characters are inserted. The value of point in the buffer has no effect
361 on printing when the stream is a marker, and this kind of printing
362 does not move point (except that if the marker points at or before the
363 position of point, point advances with the surrounding text, as
367 @cindex function output stream
368 The output characters are passed to @var{function}, which is responsible
369 for storing them away. It is called with a single character as
370 argument, as many times as there are characters to be output, and
371 is responsible for storing the characters wherever you want to put them.
374 @cindex @code{t} output stream
375 The output characters are displayed in the echo area.
378 @cindex @code{nil} output stream
379 @code{nil} specified as an output stream means to use the value of
380 @code{standard-output} instead; that value is the @dfn{default output
381 stream}, and must not be @code{nil}.
384 A symbol as output stream is equivalent to the symbol's function
388 Many of the valid output streams are also valid as input streams. The
389 difference between input and output streams is therefore more a matter
390 of how you use a Lisp object, than of different types of object.
392 Here is an example of a buffer used as an output stream. Point is
393 initially located as shown immediately before the @samp{h} in
394 @samp{the}. At the end, point is located directly before that same
397 @cindex print example
400 ---------- Buffer: foo ----------
401 This is t@point{}he contents of foo.
402 ---------- Buffer: foo ----------
405 (print "This is the output" (get-buffer "foo"))
406 @result{} "This is the output"
409 ---------- Buffer: foo ----------
412 @point{}he contents of foo.
413 ---------- Buffer: foo ----------
417 Now we show a use of a marker as an output stream. Initially, the
418 marker is in buffer @code{foo}, between the @samp{t} and the @samp{h} in
419 the word @samp{the}. At the end, the marker has advanced over the
420 inserted text so that it remains positioned before the same @samp{h}.
421 Note that the location of point, shown in the usual fashion, has no
426 ---------- Buffer: foo ----------
427 This is the @point{}output
428 ---------- Buffer: foo ----------
432 (setq m (copy-marker 10))
433 @result{} #<marker at 10 in foo>
437 (print "More output for foo." m)
438 @result{} "More output for foo."
442 ---------- Buffer: foo ----------
444 "More output for foo."
446 ---------- Buffer: foo ----------
451 @result{} #<marker at 34 in foo>
455 The following example shows output to the echo area:
459 (print "Echo Area output" t)
460 @result{} "Echo Area output"
461 ---------- Echo Area ----------
463 ---------- Echo Area ----------
467 Finally, we show the use of a function as an output stream. The
468 function @code{eat-output} takes each character that it is given and
469 conses it onto the front of the list @code{last-output} (@pxref{Building
470 Lists}). At the end, the list contains all the characters output, but
475 (setq last-output nil)
480 (defun eat-output (c)
481 (setq last-output (cons c last-output)))
486 (print "This is the output" 'eat-output)
487 @result{} "This is the output"
492 @result{} (10 34 116 117 112 116 117 111 32 101 104
493 116 32 115 105 32 115 105 104 84 34 10)
498 Now we can put the output in the proper order by reversing the list:
502 (concat (nreverse last-output))
504 \"This is the output\"
510 Calling @code{concat} converts the list to a string so you can see its
511 contents more clearly.
513 @node Output Functions
514 @section Output Functions
516 This section describes the Lisp functions for printing Lisp
517 objects---converting objects into their printed representation.
519 @cindex @samp{"} in printing
520 @cindex @samp{\} in printing
521 @cindex quoting characters in printing
522 @cindex escape characters in printing
523 Some of the Emacs printing functions add quoting characters to the
524 output when necessary so that it can be read properly. The quoting
525 characters used are @samp{"} and @samp{\}; they distinguish strings from
526 symbols, and prevent punctuation characters in strings and symbols from
527 being taken as delimiters when reading. @xref{Printed Representation},
528 for full details. You specify quoting or no quoting by the choice of
531 If the text is to be read back into Lisp, then you should print with
532 quoting characters to avoid ambiguity. Likewise, if the purpose is to
533 describe a Lisp object clearly for a Lisp programmer. However, if the
534 purpose of the output is to look nice for humans, then it is usually
535 better to print without quoting.
537 Lisp objects can refer to themselves. Printing a self-referential
538 object in the normal way would require an infinite amount of text, and
539 the attempt could cause infinite recursion. Emacs detects such
540 recursion and prints @samp{#@var{level}} instead of recursively printing
541 an object already being printed. For example, here @samp{#0} indicates
542 a recursive reference to the object at level 0 of the current print
546 (setq foo (list nil))
552 In the functions below, @var{stream} stands for an output stream.
553 (See the previous section for a description of output streams.) If
554 @var{stream} is @code{nil} or omitted, it defaults to the value of
555 @code{standard-output}.
557 @defun print object &optional stream
559 The @code{print} function is a convenient way of printing. It outputs
560 the printed representation of @var{object} to @var{stream}, printing in
561 addition one newline before @var{object} and another after it. Quoting
562 characters are used. @code{print} returns @var{object}. For example:
566 (progn (print 'The\ cat\ in)
568 (print " came back"))
570 @print{} The\ cat\ in
574 @print{} " came back"
575 @result{} " came back"
580 @defun prin1 object &optional stream
581 This function outputs the printed representation of @var{object} to
582 @var{stream}. It does not print newlines to separate output as
583 @code{print} does, but it does use quoting characters just like
584 @code{print}. It returns @var{object}.
588 (progn (prin1 'The\ cat\ in)
590 (prin1 " came back"))
591 @print{} The\ cat\ in"the hat"" came back"
592 @result{} " came back"
597 @defun princ object &optional stream
598 This function outputs the printed representation of @var{object} to
599 @var{stream}. It returns @var{object}.
601 This function is intended to produce output that is readable by people,
602 not by @code{read}, so it doesn't insert quoting characters and doesn't
603 put double-quotes around the contents of strings. It does not add any
604 spacing between calls.
610 (princ " in the \"hat\""))
611 @print{} The cat in the "hat"
612 @result{} " in the \"hat\""
617 @defun terpri &optional stream
618 @cindex newline in print
619 This function outputs a newline to @var{stream}. The name stands
620 for ``terminate print''.
623 @defun write-char character &optional stream
624 This function outputs @var{character} to @var{stream}. It returns
628 @defun prin1-to-string object &optional noescape
629 @cindex object to string
630 This function returns a string containing the text that @code{prin1}
631 would have printed for the same argument.
635 (prin1-to-string 'foo)
639 (prin1-to-string (mark-marker))
640 @result{} "#<marker at 2773 in strings.texi>"
644 If @var{noescape} is non-@code{nil}, that inhibits use of quoting
645 characters in the output. (This argument is supported in Emacs versions
650 (prin1-to-string "foo")
654 (prin1-to-string "foo" t)
659 See @code{format}, in @ref{Formatting Strings}, for other ways to obtain
660 the printed representation of a Lisp object as a string.
663 @defmac with-output-to-string body@dots{}
664 This macro executes the @var{body} forms with @code{standard-output} set
665 up to feed output into a string. Then it returns that string.
667 For example, if the current buffer name is @samp{foo},
670 (with-output-to-string
671 (princ "The buffer is ")
672 (princ (buffer-name)))
676 returns @code{"The buffer is foo"}.
679 @defun pp object &optional stream
680 This function outputs @var{object} to @var{stream}, just like
681 @code{prin1}, but does it in a more ``pretty'' way. That is, it'll
682 indent and fill the object to make it more readable for humans.
685 @node Output Variables
686 @section Variables Affecting Output
687 @cindex output-controlling variables
689 @defvar standard-output
690 The value of this variable is the default output stream---the stream
691 that print functions use when the @var{stream} argument is @code{nil}.
692 The default is @code{t}, meaning display in the echo area.
696 If this is non-@code{nil}, that means to print quoted forms using
697 abbreviated reader syntax, e.g.@: @code{(quote foo)} prints as
698 @code{'foo}, and @code{(function foo)} as @code{#'foo}.
701 @defvar print-escape-newlines
702 @cindex @samp{\n} in print
703 @cindex escape characters
704 If this variable is non-@code{nil}, then newline characters in strings
705 are printed as @samp{\n} and formfeeds are printed as @samp{\f}.
706 Normally these characters are printed as actual newlines and formfeeds.
708 This variable affects the print functions @code{prin1} and @code{print}
709 that print with quoting. It does not affect @code{princ}. Here is an
710 example using @code{prin1}:
722 (let ((print-escape-newlines t))
731 In the second expression, the local binding of
732 @code{print-escape-newlines} is in effect during the call to
733 @code{prin1}, but not during the printing of the result.
736 @defvar print-escape-nonascii
737 If this variable is non-@code{nil}, then unibyte non-@acronym{ASCII}
738 characters in strings are unconditionally printed as backslash sequences
739 by the print functions @code{prin1} and @code{print} that print with
742 Those functions also use backslash sequences for unibyte non-@acronym{ASCII}
743 characters, regardless of the value of this variable, when the output
744 stream is a multibyte buffer or a marker pointing into one.
747 @defvar print-escape-multibyte
748 If this variable is non-@code{nil}, then multibyte non-@acronym{ASCII}
749 characters in strings are unconditionally printed as backslash sequences
750 by the print functions @code{prin1} and @code{print} that print with
753 Those functions also use backslash sequences for multibyte
754 non-@acronym{ASCII} characters, regardless of the value of this variable,
755 when the output stream is a unibyte buffer or a marker pointing into
760 @cindex printing limits
761 The value of this variable is the maximum number of elements to print in
762 any list, vector or bool-vector. If an object being printed has more
763 than this many elements, it is abbreviated with an ellipsis.
765 If the value is @code{nil} (the default), then there is no limit.
769 (setq print-length 2)
781 The value of this variable is the maximum depth of nesting of
782 parentheses and brackets when printed. Any list or vector at a depth
783 exceeding this limit is abbreviated with an ellipsis. A value of
784 @code{nil} (which is the default) means no limit.
787 @defopt eval-expression-print-length
788 @defoptx eval-expression-print-level
789 These are the values for @code{print-length} and @code{print-level}
790 used by @code{eval-expression}, and thus, indirectly, by many
791 interactive evaluation commands (@pxref{Lisp Eval,, Evaluating
792 Emacs-Lisp Expressions, emacs, The GNU Emacs Manual}).
795 These variables are used for detecting and reporting circular
796 and shared structure:
799 If non-@code{nil}, this variable enables detection of circular and
800 shared structure in printing. @xref{Circular Objects}.
804 If non-@code{nil}, this variable enables detection of uninterned symbols
805 (@pxref{Creating Symbols}) in printing. When this is enabled,
806 uninterned symbols print with the prefix @samp{#:}, which tells the Lisp
807 reader to produce an uninterned symbol.
810 @defvar print-continuous-numbering
811 If non-@code{nil}, that means number continuously across print calls.
812 This affects the numbers printed for @samp{#@var{n}=} labels and
813 @samp{#@var{m}#} references.
814 Don't set this variable with @code{setq}; you should only bind it
815 temporarily to @code{t} with @code{let}. When you do that, you should
816 also bind @code{print-number-table} to @code{nil}.
819 @defvar print-number-table
820 This variable holds a vector used internally by printing to implement
821 the @code{print-circle} feature. You should not use it except
822 to bind it to @code{nil} when you bind @code{print-continuous-numbering}.
825 @defvar float-output-format
826 This variable specifies how to print floating point numbers. The
827 default is @code{nil}, meaning use the shortest output
828 that represents the number without losing information.
830 To control output format more precisely, you can put a string in this
831 variable. The string should hold a @samp{%}-specification to be used
832 in the C function @code{sprintf}. For further restrictions on what
833 you can use, see the variable's documentation string.