2 @c This is part of the GNU Emacs Lisp Reference Manual.
3 @c Copyright (C) 1990-1994, 1998-1999, 2001-2015 Free Software
5 @c See the file elisp.texi for copying conditions.
7 @chapter Reading and Printing Lisp Objects
9 @dfn{Printing} and @dfn{reading} are the operations of converting Lisp
10 objects to textual form and vice versa. They use the printed
11 representations and read syntax described in @ref{Lisp Data Types}.
13 This chapter describes the Lisp functions for reading and printing.
14 It also describes @dfn{streams}, which specify where to get the text (if
15 reading) or where to put it (if printing).
18 * Streams Intro:: Overview of streams, reading and printing.
19 * Input Streams:: Various data types that can be used as input streams.
20 * Input Functions:: Functions to read Lisp objects from text.
21 * Output Streams:: Various data types that can be used as output streams.
22 * Output Functions:: Functions to print Lisp objects as text.
23 * Output Variables:: Variables that control what the printing functions do.
27 @section Introduction to Reading and Printing
32 @dfn{Reading} a Lisp object means parsing a Lisp expression in textual
33 form and producing a corresponding Lisp object. This is how Lisp
34 programs get into Lisp from files of Lisp code. We call the text the
35 @dfn{read syntax} of the object. For example, the text @samp{(a .@: 5)}
36 is the read syntax for a cons cell whose @sc{car} is @code{a} and whose
37 @sc{cdr} is the number 5.
39 @dfn{Printing} a Lisp object means producing text that represents that
40 object---converting the object to its @dfn{printed representation}
41 (@pxref{Printed Representation}). Printing the cons cell described
42 above produces the text @samp{(a .@: 5)}.
44 Reading and printing are more or less inverse operations: printing the
45 object that results from reading a given piece of text often produces
46 the same text, and reading the text that results from printing an object
47 usually produces a similar-looking object. For example, printing the
48 symbol @code{foo} produces the text @samp{foo}, and reading that text
49 returns the symbol @code{foo}. Printing a list whose elements are
50 @code{a} and @code{b} produces the text @samp{(a b)}, and reading that
51 text produces a list (but not the same list) with elements @code{a}
54 However, these two operations are not precisely inverse to each other.
55 There are three kinds of exceptions:
59 Printing can produce text that cannot be read. For example, buffers,
60 windows, frames, subprocesses and markers print as text that starts
61 with @samp{#}; if you try to read this text, you get an error. There is
62 no way to read those data types.
65 One object can have multiple textual representations. For example,
66 @samp{1} and @samp{01} represent the same integer, and @samp{(a b)} and
67 @samp{(a .@: (b))} represent the same list. Reading will accept any of
68 the alternatives, but printing must choose one of them.
71 Comments can appear at certain points in the middle of an object's
72 read sequence without affecting the result of reading it.
76 @section Input Streams
77 @cindex stream (for reading)
80 Most of the Lisp functions for reading text take an @dfn{input stream}
81 as an argument. The input stream specifies where or how to get the
82 characters of the text to be read. Here are the possible types of input
87 @cindex buffer input stream
88 The input characters are read from @var{buffer}, starting with the
89 character directly after point. Point advances as characters are read.
92 @cindex marker input stream
93 The input characters are read from the buffer that @var{marker} is in,
94 starting with the character directly after the marker. The marker
95 position advances as characters are read. The value of point in the
96 buffer has no effect when the stream is a marker.
99 @cindex string input stream
100 The input characters are taken from @var{string}, starting at the first
101 character in the string and using as many characters as required.
104 @cindex function input stream
105 The input characters are generated by @var{function}, which must support
110 When it is called with no arguments, it should return the next character.
113 When it is called with one argument (always a character), @var{function}
114 should save the argument and arrange to return it on the next call.
115 This is called @dfn{unreading} the character; it happens when the Lisp
116 reader reads one character too many and wants to ``put it back where it
117 came from''. In this case, it makes no difference what value
118 @var{function} returns.
122 @cindex @code{t} input stream
123 @code{t} used as a stream means that the input is read from the
124 minibuffer. In fact, the minibuffer is invoked once and the text
125 given by the user is made into a string that is then used as the
126 input stream. If Emacs is running in batch mode, standard input is used
127 instead of the minibuffer. For example,
129 (message "%s" (read t))
131 will read a Lisp expression from standard input and print the result
135 @cindex @code{nil} input stream
136 @code{nil} supplied as an input stream means to use the value of
137 @code{standard-input} instead; that value is the @dfn{default input
138 stream}, and must be a non-@code{nil} input stream.
141 A symbol as input stream is equivalent to the symbol's function
145 Here is an example of reading from a stream that is a buffer, showing
146 where point is located before and after:
150 ---------- Buffer: foo ----------
151 This@point{} is the contents of foo.
152 ---------- Buffer: foo ----------
156 (read (get-buffer "foo"))
160 (read (get-buffer "foo"))
165 ---------- Buffer: foo ----------
166 This is the@point{} contents of foo.
167 ---------- Buffer: foo ----------
172 Note that the first read skips a space. Reading skips any amount of
173 whitespace preceding the significant text.
175 Here is an example of reading from a stream that is a marker,
176 initially positioned at the beginning of the buffer shown. The value
177 read is the symbol @code{This}.
182 ---------- Buffer: foo ----------
183 This is the contents of foo.
184 ---------- Buffer: foo ----------
188 (setq m (set-marker (make-marker) 1 (get-buffer "foo")))
189 @result{} #<marker at 1 in foo>
197 @result{} #<marker at 5 in foo> ;; @r{Before the first space.}
201 Here we read from the contents of a string:
205 (read "(When in) the course")
210 The following example reads from the minibuffer. The
211 prompt is: @w{@samp{Lisp expression: }}. (That is always the prompt
212 used when you read from the stream @code{t}.) The user's input is shown
213 following the prompt.
219 ---------- Buffer: Minibuffer ----------
220 Lisp expression: @kbd{23 @key{RET}}
221 ---------- Buffer: Minibuffer ----------
225 Finally, here is an example of a stream that is a function, named
226 @code{useless-stream}. Before we use the stream, we initialize the
227 variable @code{useless-list} to a list of characters. Then each call to
228 the function @code{useless-stream} obtains the next character in the list
229 or unreads a character by adding it to the front of the list.
233 (setq useless-list (append "XY()" nil))
234 @result{} (88 89 40 41)
238 (defun useless-stream (&optional unread)
240 (setq useless-list (cons unread useless-list))
241 (prog1 (car useless-list)
242 (setq useless-list (cdr useless-list)))))
243 @result{} useless-stream
248 Now we read using the stream thus constructed:
252 (read 'useless-stream)
263 Note that the open and close parentheses remain in the list. The Lisp
264 reader encountered the open parenthesis, decided that it ended the
265 input, and unread it. Another attempt to read from the stream at this
266 point would read @samp{()} and return @code{nil}.
268 @node Input Functions
269 @section Input Functions
271 This section describes the Lisp functions and variables that pertain
274 In the functions below, @var{stream} stands for an input stream (see
275 the previous section). If @var{stream} is @code{nil} or omitted, it
276 defaults to the value of @code{standard-input}.
279 An @code{end-of-file} error is signaled if reading encounters an
280 unterminated list, vector, or string.
282 @defun read &optional stream
283 This function reads one textual Lisp expression from @var{stream},
284 returning it as a Lisp object. This is the basic Lisp input function.
287 @defun read-from-string string &optional start end
288 @cindex string to object
289 This function reads the first textual Lisp expression from the text in
290 @var{string}. It returns a cons cell whose @sc{car} is that expression,
291 and whose @sc{cdr} is an integer giving the position of the next
292 remaining character in the string (i.e., the first one not read).
294 If @var{start} is supplied, then reading begins at index @var{start} in
295 the string (where the first character is at index 0). If you specify
296 @var{end}, then reading is forced to stop just before that index, as if
297 the rest of the string were not there.
303 (read-from-string "(setq x 55) (setq y 5)")
304 @result{} ((setq x 55) . 11)
307 (read-from-string "\"A short string\"")
308 @result{} ("A short string" . 16)
312 ;; @r{Read starting at the first character.}
313 (read-from-string "(list 112)" 0)
314 @result{} ((list 112) . 10)
317 ;; @r{Read starting at the second character.}
318 (read-from-string "(list 112)" 1)
322 ;; @r{Read starting at the seventh character,}
323 ;; @r{and stopping at the ninth.}
324 (read-from-string "(list 112)" 6 8)
330 @defvar standard-input
331 This variable holds the default input stream---the stream that
332 @code{read} uses when the @var{stream} argument is @code{nil}.
333 The default is @code{t}, meaning use the minibuffer.
337 If non-@code{nil}, this variable enables the reading of circular and
338 shared structures. @xref{Circular Objects}. Its default value is
342 @cindex binary I/O in batch mode
343 When reading or writing from the standard input/output streams of the
344 Emacs process in batch mode, it is sometimes required to make sure any
345 arbitrary binary data will be read/written verbatim, and/or that no
346 translation of newlines to or from CR-LF pairs are performed. This
347 issue does not exist on Posix hosts, only on MS-Windows and MS-DOS@.
348 The following function allows to control the I/O mode of any standard
349 stream of the Emacs process.
351 @defun set-binary-mode stream mode
352 Switch @var{stream} into binary or text I/O mode. If @var{mode} is
353 non-@code{nil}, switch to binary mode, otherwise switch to text mode.
354 The value of @var{stream} can be one of @code{stdin}, @code{stdout},
355 or @code{stderr}. This function flushes any pending output data of
356 @var{stream} as a side effect, and returns the previous value of I/O
357 mode for @var{stream}. On Posix hosts, it always returns a
358 non-@code{nil} value and does nothing except flushing pending output.
362 @section Output Streams
363 @cindex stream (for printing)
364 @cindex output stream
366 An output stream specifies what to do with the characters produced
367 by printing. Most print functions accept an output stream as an
368 optional argument. Here are the possible types of output stream:
372 @cindex buffer output stream
373 The output characters are inserted into @var{buffer} at point.
374 Point advances as characters are inserted.
377 @cindex marker output stream
378 The output characters are inserted into the buffer that @var{marker}
379 points into, at the marker position. The marker position advances as
380 characters are inserted. The value of point in the buffer has no effect
381 on printing when the stream is a marker, and this kind of printing
382 does not move point (except that if the marker points at or before the
383 position of point, point advances with the surrounding text, as
387 @cindex function output stream
388 The output characters are passed to @var{function}, which is responsible
389 for storing them away. It is called with a single character as
390 argument, as many times as there are characters to be output, and
391 is responsible for storing the characters wherever you want to put them.
394 @cindex @code{t} output stream
395 The output characters are displayed in the echo area.
398 @cindex @code{nil} output stream
399 @code{nil} specified as an output stream means to use the value of
400 @code{standard-output} instead; that value is the @dfn{default output
401 stream}, and must not be @code{nil}.
404 A symbol as output stream is equivalent to the symbol's function
408 Many of the valid output streams are also valid as input streams. The
409 difference between input and output streams is therefore more a matter
410 of how you use a Lisp object, than of different types of object.
412 Here is an example of a buffer used as an output stream. Point is
413 initially located as shown immediately before the @samp{h} in
414 @samp{the}. At the end, point is located directly before that same
417 @cindex print example
420 ---------- Buffer: foo ----------
421 This is t@point{}he contents of foo.
422 ---------- Buffer: foo ----------
425 (print "This is the output" (get-buffer "foo"))
426 @result{} "This is the output"
429 ---------- Buffer: foo ----------
432 @point{}he contents of foo.
433 ---------- Buffer: foo ----------
437 Now we show a use of a marker as an output stream. Initially, the
438 marker is in buffer @code{foo}, between the @samp{t} and the @samp{h} in
439 the word @samp{the}. At the end, the marker has advanced over the
440 inserted text so that it remains positioned before the same @samp{h}.
441 Note that the location of point, shown in the usual fashion, has no
446 ---------- Buffer: foo ----------
447 This is the @point{}output
448 ---------- Buffer: foo ----------
452 (setq m (copy-marker 10))
453 @result{} #<marker at 10 in foo>
457 (print "More output for foo." m)
458 @result{} "More output for foo."
462 ---------- Buffer: foo ----------
464 "More output for foo."
466 ---------- Buffer: foo ----------
471 @result{} #<marker at 34 in foo>
475 The following example shows output to the echo area:
479 (print "Echo Area output" t)
480 @result{} "Echo Area output"
481 ---------- Echo Area ----------
483 ---------- Echo Area ----------
487 Finally, we show the use of a function as an output stream. The
488 function @code{eat-output} takes each character that it is given and
489 conses it onto the front of the list @code{last-output} (@pxref{Building
490 Lists}). At the end, the list contains all the characters output, but
495 (setq last-output nil)
500 (defun eat-output (c)
501 (setq last-output (cons c last-output)))
506 (print "This is the output" 'eat-output)
507 @result{} "This is the output"
512 @result{} (10 34 116 117 112 116 117 111 32 101 104
513 116 32 115 105 32 115 105 104 84 34 10)
518 Now we can put the output in the proper order by reversing the list:
522 (concat (nreverse last-output))
524 \"This is the output\"
530 Calling @code{concat} converts the list to a string so you can see its
531 contents more clearly.
533 @node Output Functions
534 @section Output Functions
536 This section describes the Lisp functions for printing Lisp
537 objects---converting objects into their printed representation.
539 @cindex @samp{"} in printing
540 @cindex @samp{\} in printing
541 @cindex quoting characters in printing
542 @cindex escape characters in printing
543 Some of the Emacs printing functions add quoting characters to the
544 output when necessary so that it can be read properly. The quoting
545 characters used are @samp{"} and @samp{\}; they distinguish strings from
546 symbols, and prevent punctuation characters in strings and symbols from
547 being taken as delimiters when reading. @xref{Printed Representation},
548 for full details. You specify quoting or no quoting by the choice of
551 If the text is to be read back into Lisp, then you should print with
552 quoting characters to avoid ambiguity. Likewise, if the purpose is to
553 describe a Lisp object clearly for a Lisp programmer. However, if the
554 purpose of the output is to look nice for humans, then it is usually
555 better to print without quoting.
557 Lisp objects can refer to themselves. Printing a self-referential
558 object in the normal way would require an infinite amount of text, and
559 the attempt could cause infinite recursion. Emacs detects such
560 recursion and prints @samp{#@var{level}} instead of recursively printing
561 an object already being printed. For example, here @samp{#0} indicates
562 a recursive reference to the object at level 0 of the current print
566 (setq foo (list nil))
572 In the functions below, @var{stream} stands for an output stream.
573 (See the previous section for a description of output streams.) If
574 @var{stream} is @code{nil} or omitted, it defaults to the value of
575 @code{standard-output}.
577 @defun print object &optional stream
579 The @code{print} function is a convenient way of printing. It outputs
580 the printed representation of @var{object} to @var{stream}, printing in
581 addition one newline before @var{object} and another after it. Quoting
582 characters are used. @code{print} returns @var{object}. For example:
586 (progn (print 'The\ cat\ in)
588 (print " came back"))
590 @print{} The\ cat\ in
594 @print{} " came back"
595 @result{} " came back"
600 @defun prin1 object &optional stream
601 This function outputs the printed representation of @var{object} to
602 @var{stream}. It does not print newlines to separate output as
603 @code{print} does, but it does use quoting characters just like
604 @code{print}. It returns @var{object}.
608 (progn (prin1 'The\ cat\ in)
610 (prin1 " came back"))
611 @print{} The\ cat\ in"the hat"" came back"
612 @result{} " came back"
617 @defun princ object &optional stream
618 This function outputs the printed representation of @var{object} to
619 @var{stream}. It returns @var{object}.
621 This function is intended to produce output that is readable by people,
622 not by @code{read}, so it doesn't insert quoting characters and doesn't
623 put double-quotes around the contents of strings. It does not add any
624 spacing between calls.
630 (princ " in the \"hat\""))
631 @print{} The cat in the "hat"
632 @result{} " in the \"hat\""
637 @defun terpri &optional stream ensure
638 @cindex newline in print
639 This function outputs a newline to @var{stream}. The name stands for
640 ``terminate print''. If @var{ensure} is non-@code{nil} no newline is printed
641 if @var{stream} is already at the beginning of a line. Note in this
642 case @var{stream} can not be a function and an error is signalled if
643 it is. This function returns @code{t} if a newline is printed.
646 @defun write-char character &optional stream
647 This function outputs @var{character} to @var{stream}. It returns
651 @defun prin1-to-string object &optional noescape
652 @cindex object to string
653 This function returns a string containing the text that @code{prin1}
654 would have printed for the same argument.
658 (prin1-to-string 'foo)
662 (prin1-to-string (mark-marker))
663 @result{} "#<marker at 2773 in strings.texi>"
667 If @var{noescape} is non-@code{nil}, that inhibits use of quoting
668 characters in the output. (This argument is supported in Emacs versions
673 (prin1-to-string "foo")
677 (prin1-to-string "foo" t)
682 See @code{format}, in @ref{Formatting Strings}, for other ways to obtain
683 the printed representation of a Lisp object as a string.
686 @defmac with-output-to-string body@dots{}
687 This macro executes the @var{body} forms with @code{standard-output} set
688 up to feed output into a string. Then it returns that string.
690 For example, if the current buffer name is @samp{foo},
693 (with-output-to-string
694 (princ "The buffer is ")
695 (princ (buffer-name)))
699 returns @code{"The buffer is foo"}.
702 @defun pp object &optional stream
703 This function outputs @var{object} to @var{stream}, just like
704 @code{prin1}, but does it in a more ``pretty'' way. That is, it'll
705 indent and fill the object to make it more readable for humans.
708 If you need to use binary I/O in batch mode, e.g., use the functions
709 described in this section to write out arbitrary binary data or avoid
710 conversion of newlines on non-Posix hosts, see @ref{Input Functions,
713 @node Output Variables
714 @section Variables Affecting Output
715 @cindex output-controlling variables
717 @defvar standard-output
718 The value of this variable is the default output stream---the stream
719 that print functions use when the @var{stream} argument is @code{nil}.
720 The default is @code{t}, meaning display in the echo area.
724 If this is non-@code{nil}, that means to print quoted forms using
725 abbreviated reader syntax, e.g., @code{(quote foo)} prints as
726 @code{'foo}, and @code{(function foo)} as @code{#'foo}.
729 @defvar print-escape-newlines
730 @cindex @samp{\n} in print
731 @cindex escape characters
732 If this variable is non-@code{nil}, then newline characters in strings
733 are printed as @samp{\n} and formfeeds are printed as @samp{\f}.
734 Normally these characters are printed as actual newlines and formfeeds.
736 This variable affects the print functions @code{prin1} and @code{print}
737 that print with quoting. It does not affect @code{princ}. Here is an
738 example using @code{prin1}:
750 (let ((print-escape-newlines t))
759 In the second expression, the local binding of
760 @code{print-escape-newlines} is in effect during the call to
761 @code{prin1}, but not during the printing of the result.
764 @defvar print-escape-nonascii
765 If this variable is non-@code{nil}, then unibyte non-@acronym{ASCII}
766 characters in strings are unconditionally printed as backslash sequences
767 by the print functions @code{prin1} and @code{print} that print with
770 Those functions also use backslash sequences for unibyte non-@acronym{ASCII}
771 characters, regardless of the value of this variable, when the output
772 stream is a multibyte buffer or a marker pointing into one.
775 @defvar print-escape-multibyte
776 If this variable is non-@code{nil}, then multibyte non-@acronym{ASCII}
777 characters in strings are unconditionally printed as backslash sequences
778 by the print functions @code{prin1} and @code{print} that print with
781 Those functions also use backslash sequences for multibyte
782 non-@acronym{ASCII} characters, regardless of the value of this variable,
783 when the output stream is a unibyte buffer or a marker pointing into
788 @cindex printing limits
789 The value of this variable is the maximum number of elements to print in
790 any list, vector or bool-vector. If an object being printed has more
791 than this many elements, it is abbreviated with an ellipsis.
793 If the value is @code{nil} (the default), then there is no limit.
797 (setq print-length 2)
809 The value of this variable is the maximum depth of nesting of
810 parentheses and brackets when printed. Any list or vector at a depth
811 exceeding this limit is abbreviated with an ellipsis. A value of
812 @code{nil} (which is the default) means no limit.
815 @defopt eval-expression-print-length
816 @defoptx eval-expression-print-level
817 These are the values for @code{print-length} and @code{print-level}
818 used by @code{eval-expression}, and thus, indirectly, by many
819 interactive evaluation commands (@pxref{Lisp Eval,, Evaluating
820 Emacs-Lisp Expressions, emacs, The GNU Emacs Manual}).
823 These variables are used for detecting and reporting circular
824 and shared structure:
827 If non-@code{nil}, this variable enables detection of circular and
828 shared structure in printing. @xref{Circular Objects}.
832 If non-@code{nil}, this variable enables detection of uninterned symbols
833 (@pxref{Creating Symbols}) in printing. When this is enabled,
834 uninterned symbols print with the prefix @samp{#:}, which tells the Lisp
835 reader to produce an uninterned symbol.
838 @defvar print-continuous-numbering
839 If non-@code{nil}, that means number continuously across print calls.
840 This affects the numbers printed for @samp{#@var{n}=} labels and
841 @samp{#@var{m}#} references.
842 Don't set this variable with @code{setq}; you should only bind it
843 temporarily to @code{t} with @code{let}. When you do that, you should
844 also bind @code{print-number-table} to @code{nil}.
847 @defvar print-number-table
848 This variable holds a vector used internally by printing to implement
849 the @code{print-circle} feature. You should not use it except
850 to bind it to @code{nil} when you bind @code{print-continuous-numbering}.
853 @defvar float-output-format
854 This variable specifies how to print floating-point numbers. The
855 default is @code{nil}, meaning use the shortest output
856 that represents the number without losing information.
858 To control output format more precisely, you can put a string in this
859 variable. The string should hold a @samp{%}-specification to be used
860 in the C function @code{sprintf}. For further restrictions on what
861 you can use, see the variable's documentation string.