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.
5 @setfilename ../../info/streams
6 @node Read and Print, Minibuffers, Debugging, Top
7 @comment node-name, next, previous, up
8 @chapter Reading and Printing Lisp Objects
10 @dfn{Printing} and @dfn{reading} are the operations of converting Lisp
11 objects to textual form and vice versa. They use the printed
12 representations and read syntax described in @ref{Lisp Data Types}.
14 This chapter describes the Lisp functions for reading and printing.
15 It also describes @dfn{streams}, which specify where to get the text (if
16 reading) or where to put it (if printing).
19 * Streams Intro:: Overview of streams, reading and printing.
20 * Input Streams:: Various data types that can be used as input streams.
21 * Input Functions:: Functions to read Lisp objects from text.
22 * Output Streams:: Various data types that can be used as output streams.
23 * Output Functions:: Functions to print Lisp objects as text.
24 * Output Variables:: Variables that control what the printing functions do.
28 @section Introduction to Reading and Printing
33 @dfn{Reading} a Lisp object means parsing a Lisp expression in textual
34 form and producing a corresponding Lisp object. This is how Lisp
35 programs get into Lisp from files of Lisp code. We call the text the
36 @dfn{read syntax} of the object. For example, the text @samp{(a .@: 5)}
37 is the read syntax for a cons cell whose @sc{car} is @code{a} and whose
38 @sc{cdr} is the number 5.
40 @dfn{Printing} a Lisp object means producing text that represents that
41 object---converting the object to its @dfn{printed representation}
42 (@pxref{Printed Representation}). Printing the cons cell described
43 above produces the text @samp{(a .@: 5)}.
45 Reading and printing are more or less inverse operations: printing the
46 object that results from reading a given piece of text often produces
47 the same text, and reading the text that results from printing an object
48 usually produces a similar-looking object. For example, printing the
49 symbol @code{foo} produces the text @samp{foo}, and reading that text
50 returns the symbol @code{foo}. Printing a list whose elements are
51 @code{a} and @code{b} produces the text @samp{(a b)}, and reading that
52 text produces a list (but not the same list) with elements @code{a}
55 However, these two operations are not precisely inverse to each other.
56 There are three kinds of exceptions:
60 Printing can produce text that cannot be read. For example, buffers,
61 windows, frames, subprocesses and markers print as text that starts
62 with @samp{#}; if you try to read this text, you get an error. There is
63 no way to read those data types.
66 One object can have multiple textual representations. For example,
67 @samp{1} and @samp{01} represent the same integer, and @samp{(a b)} and
68 @samp{(a .@: (b))} represent the same list. Reading will accept any of
69 the alternatives, but printing must choose one of them.
72 Comments can appear at certain points in the middle of an object's
73 read sequence without affecting the result of reading it.
77 @section Input Streams
78 @cindex stream (for reading)
81 Most of the Lisp functions for reading text take an @dfn{input stream}
82 as an argument. The input stream specifies where or how to get the
83 characters of the text to be read. Here are the possible types of input
88 @cindex buffer input stream
89 The input characters are read from @var{buffer}, starting with the
90 character directly after point. Point advances as characters are read.
93 @cindex marker input stream
94 The input characters are read from the buffer that @var{marker} is in,
95 starting with the character directly after the marker. The marker
96 position advances as characters are read. The value of point in the
97 buffer has no effect when the stream is a marker.
100 @cindex string input stream
101 The input characters are taken from @var{string}, starting at the first
102 character in the string and using as many characters as required.
105 @cindex function input stream
106 The input characters are generated by @var{function}, which must support
111 When it is called with no arguments, it should return the next character.
114 When it is called with one argument (always a character), @var{function}
115 should save the argument and arrange to return it on the next call.
116 This is called @dfn{unreading} the character; it happens when the Lisp
117 reader reads one character too many and wants to ``put it back where it
118 came from.'' In this case, it makes no difference what value
119 @var{function} returns.
123 @cindex @code{t} input stream
124 @code{t} used as a stream means that the input is read from the
125 minibuffer. In fact, the minibuffer is invoked once and the text
126 given by the user is made into a string that is then used as the
127 input stream. If Emacs is running in batch mode, standard input is used
128 instead of the minibuffer. For example,
130 (message "%s" (read t))
132 will read a Lisp expression from standard input and print the result
136 @cindex @code{nil} input stream
137 @code{nil} supplied as an input stream means to use the value of
138 @code{standard-input} instead; that value is the @dfn{default input
139 stream}, and must be a non-@code{nil} input stream.
142 A symbol as input stream is equivalent to the symbol's function
146 Here is an example of reading from a stream that is a buffer, showing
147 where point is located before and after:
151 ---------- Buffer: foo ----------
152 This@point{} is the contents of foo.
153 ---------- Buffer: foo ----------
157 (read (get-buffer "foo"))
161 (read (get-buffer "foo"))
166 ---------- Buffer: foo ----------
167 This is the@point{} contents of foo.
168 ---------- Buffer: foo ----------
173 Note that the first read skips a space. Reading skips any amount of
174 whitespace preceding the significant text.
176 Here is an example of reading from a stream that is a marker,
177 initially positioned at the beginning of the buffer shown. The value
178 read is the symbol @code{This}.
183 ---------- Buffer: foo ----------
184 This is the contents of foo.
185 ---------- Buffer: foo ----------
189 (setq m (set-marker (make-marker) 1 (get-buffer "foo")))
190 @result{} #<marker at 1 in foo>
198 @result{} #<marker at 5 in foo> ;; @r{Before the first space.}
202 Here we read from the contents of a string:
206 (read "(When in) the course")
211 The following example reads from the minibuffer. The
212 prompt is: @w{@samp{Lisp expression: }}. (That is always the prompt
213 used when you read from the stream @code{t}.) The user's input is shown
214 following the prompt.
220 ---------- Buffer: Minibuffer ----------
221 Lisp expression: @kbd{23 @key{RET}}
222 ---------- Buffer: Minibuffer ----------
226 Finally, here is an example of a stream that is a function, named
227 @code{useless-stream}. Before we use the stream, we initialize the
228 variable @code{useless-list} to a list of characters. Then each call to
229 the function @code{useless-stream} obtains the next character in the list
230 or unreads a character by adding it to the front of the list.
234 (setq useless-list (append "XY()" nil))
235 @result{} (88 89 40 41)
239 (defun useless-stream (&optional unread)
241 (setq useless-list (cons unread useless-list))
242 (prog1 (car useless-list)
243 (setq useless-list (cdr useless-list)))))
244 @result{} useless-stream
249 Now we read using the stream thus constructed:
253 (read 'useless-stream)
264 Note that the open and close parentheses remain in the list. The Lisp
265 reader encountered the open parenthesis, decided that it ended the
266 input, and unread it. Another attempt to read from the stream at this
267 point would read @samp{()} and return @code{nil}.
269 @node Input Functions
270 @section Input Functions
272 This section describes the Lisp functions and variables that pertain
275 In the functions below, @var{stream} stands for an input stream (see
276 the previous section). If @var{stream} is @code{nil} or omitted, it
277 defaults to the value of @code{standard-input}.
280 An @code{end-of-file} error is signaled if reading encounters an
281 unterminated list, vector, or string.
283 @defun read &optional stream
284 This function reads one textual Lisp expression from @var{stream},
285 returning it as a Lisp object. This is the basic Lisp input function.
288 @defun read-from-string string &optional start end
289 @cindex string to object
290 This function reads the first textual Lisp expression from the text in
291 @var{string}. It returns a cons cell whose @sc{car} is that expression,
292 and whose @sc{cdr} is an integer giving the position of the next
293 remaining character in the string (i.e., the first one not read).
295 If @var{start} is supplied, then reading begins at index @var{start} in
296 the string (where the first character is at index 0). If you specify
297 @var{end}, then reading is forced to stop just before that index, as if
298 the rest of the string were not there.
304 (read-from-string "(setq x 55) (setq y 5)")
305 @result{} ((setq x 55) . 11)
308 (read-from-string "\"A short string\"")
309 @result{} ("A short string" . 16)
313 ;; @r{Read starting at the first character.}
314 (read-from-string "(list 112)" 0)
315 @result{} ((list 112) . 10)
318 ;; @r{Read starting at the second character.}
319 (read-from-string "(list 112)" 1)
323 ;; @r{Read starting at the seventh character,}
324 ;; @r{and stopping at the ninth.}
325 (read-from-string "(list 112)" 6 8)
331 @defvar standard-input
332 This variable holds the default input stream---the stream that
333 @code{read} uses when the @var{stream} argument is @code{nil}.
334 The default is @code{t}, meaning use the minibuffer.
338 If non-@code{nil}, this variable enables the reading of circular and
339 shared structures. @xref{Circular Objects}. Its default value is
344 @section Output Streams
345 @cindex stream (for printing)
346 @cindex output stream
348 An output stream specifies what to do with the characters produced
349 by printing. Most print functions accept an output stream as an
350 optional argument. Here are the possible types of output stream:
354 @cindex buffer output stream
355 The output characters are inserted into @var{buffer} at point.
356 Point advances as characters are inserted.
359 @cindex marker output stream
360 The output characters are inserted into the buffer that @var{marker}
361 points into, at the marker position. The marker position advances as
362 characters are inserted. The value of point in the buffer has no effect
363 on printing when the stream is a marker, and this kind of printing
364 does not move point (except that if the marker points at or before the
365 position of point, point advances with the surrounding text, as
369 @cindex function output stream
370 The output characters are passed to @var{function}, which is responsible
371 for storing them away. It is called with a single character as
372 argument, as many times as there are characters to be output, and
373 is responsible for storing the characters wherever you want to put them.
376 @cindex @code{t} output stream
377 The output characters are displayed in the echo area.
380 @cindex @code{nil} output stream
381 @code{nil} specified as an output stream means to use the value of
382 @code{standard-output} instead; that value is the @dfn{default output
383 stream}, and must not be @code{nil}.
386 A symbol as output stream is equivalent to the symbol's function
390 Many of the valid output streams are also valid as input streams. The
391 difference between input and output streams is therefore more a matter
392 of how you use a Lisp object, than of different types of object.
394 Here is an example of a buffer used as an output stream. Point is
395 initially located as shown immediately before the @samp{h} in
396 @samp{the}. At the end, point is located directly before that same
399 @cindex print example
402 ---------- Buffer: foo ----------
403 This is t@point{}he contents of foo.
404 ---------- Buffer: foo ----------
407 (print "This is the output" (get-buffer "foo"))
408 @result{} "This is the output"
411 ---------- Buffer: foo ----------
414 @point{}he contents of foo.
415 ---------- Buffer: foo ----------
419 Now we show a use of a marker as an output stream. Initially, the
420 marker is in buffer @code{foo}, between the @samp{t} and the @samp{h} in
421 the word @samp{the}. At the end, the marker has advanced over the
422 inserted text so that it remains positioned before the same @samp{h}.
423 Note that the location of point, shown in the usual fashion, has no
428 ---------- Buffer: foo ----------
429 This is the @point{}output
430 ---------- Buffer: foo ----------
434 (setq m (copy-marker 10))
435 @result{} #<marker at 10 in foo>
439 (print "More output for foo." m)
440 @result{} "More output for foo."
444 ---------- Buffer: foo ----------
446 "More output for foo."
448 ---------- Buffer: foo ----------
453 @result{} #<marker at 34 in foo>
457 The following example shows output to the echo area:
461 (print "Echo Area output" t)
462 @result{} "Echo Area output"
463 ---------- Echo Area ----------
465 ---------- Echo Area ----------
469 Finally, we show the use of a function as an output stream. The
470 function @code{eat-output} takes each character that it is given and
471 conses it onto the front of the list @code{last-output} (@pxref{Building
472 Lists}). At the end, the list contains all the characters output, but
477 (setq last-output nil)
482 (defun eat-output (c)
483 (setq last-output (cons c last-output)))
488 (print "This is the output" 'eat-output)
489 @result{} "This is the output"
494 @result{} (10 34 116 117 112 116 117 111 32 101 104
495 116 32 115 105 32 115 105 104 84 34 10)
500 Now we can put the output in the proper order by reversing the list:
504 (concat (nreverse last-output))
506 \"This is the output\"
512 Calling @code{concat} converts the list to a string so you can see its
513 contents more clearly.
515 @node Output Functions
516 @section Output Functions
518 This section describes the Lisp functions for printing Lisp
519 objects---converting objects into their printed representation.
521 @cindex @samp{"} in printing
522 @cindex @samp{\} in printing
523 @cindex quoting characters in printing
524 @cindex escape characters in printing
525 Some of the Emacs printing functions add quoting characters to the
526 output when necessary so that it can be read properly. The quoting
527 characters used are @samp{"} and @samp{\}; they distinguish strings from
528 symbols, and prevent punctuation characters in strings and symbols from
529 being taken as delimiters when reading. @xref{Printed Representation},
530 for full details. You specify quoting or no quoting by the choice of
533 If the text is to be read back into Lisp, then you should print with
534 quoting characters to avoid ambiguity. Likewise, if the purpose is to
535 describe a Lisp object clearly for a Lisp programmer. However, if the
536 purpose of the output is to look nice for humans, then it is usually
537 better to print without quoting.
539 Lisp objects can refer to themselves. Printing a self-referential
540 object in the normal way would require an infinite amount of text, and
541 the attempt could cause infinite recursion. Emacs detects such
542 recursion and prints @samp{#@var{level}} instead of recursively printing
543 an object already being printed. For example, here @samp{#0} indicates
544 a recursive reference to the object at level 0 of the current print
548 (setq foo (list nil))
554 In the functions below, @var{stream} stands for an output stream.
555 (See the previous section for a description of output streams.) If
556 @var{stream} is @code{nil} or omitted, it defaults to the value of
557 @code{standard-output}.
559 @defun print object &optional stream
561 The @code{print} function is a convenient way of printing. It outputs
562 the printed representation of @var{object} to @var{stream}, printing in
563 addition one newline before @var{object} and another after it. Quoting
564 characters are used. @code{print} returns @var{object}. For example:
568 (progn (print 'The\ cat\ in)
570 (print " came back"))
572 @print{} The\ cat\ in
576 @print{} " came back"
577 @result{} " came back"
582 @defun prin1 object &optional stream
583 This function outputs the printed representation of @var{object} to
584 @var{stream}. It does not print newlines to separate output as
585 @code{print} does, but it does use quoting characters just like
586 @code{print}. It returns @var{object}.
590 (progn (prin1 'The\ cat\ in)
592 (prin1 " came back"))
593 @print{} The\ cat\ in"the hat"" came back"
594 @result{} " came back"
599 @defun princ object &optional stream
600 This function outputs the printed representation of @var{object} to
601 @var{stream}. It returns @var{object}.
603 This function is intended to produce output that is readable by people,
604 not by @code{read}, so it doesn't insert quoting characters and doesn't
605 put double-quotes around the contents of strings. It does not add any
606 spacing between calls.
612 (princ " in the \"hat\""))
613 @print{} The cat in the "hat"
614 @result{} " in the \"hat\""
619 @defun terpri &optional stream
620 @cindex newline in print
621 This function outputs a newline to @var{stream}. The name stands
622 for ``terminate print.''
625 @defun write-char character &optional stream
626 This function outputs @var{character} to @var{stream}. It returns
630 @defun prin1-to-string object &optional noescape
631 @cindex object to string
632 This function returns a string containing the text that @code{prin1}
633 would have printed for the same argument.
637 (prin1-to-string 'foo)
641 (prin1-to-string (mark-marker))
642 @result{} "#<marker at 2773 in strings.texi>"
646 If @var{noescape} is non-@code{nil}, that inhibits use of quoting
647 characters in the output. (This argument is supported in Emacs versions
652 (prin1-to-string "foo")
656 (prin1-to-string "foo" t)
661 See @code{format}, in @ref{Formatting Strings}, for other ways to obtain
662 the printed representation of a Lisp object as a string.
665 @defmac with-output-to-string body@dots{}
666 This macro executes the @var{body} forms with @code{standard-output} set
667 up to feed output into a string. Then it returns that string.
669 For example, if the current buffer name is @samp{foo},
672 (with-output-to-string
673 (princ "The buffer is ")
674 (princ (buffer-name)))
678 returns @code{"The buffer is foo"}.
681 @defun pp object &optional stream
682 This function outputs @var{object} to @var{stream}, just like
683 @code{prin1}, but does it in a more ``pretty'' way. That is, it'll
684 indent and fill the object to make it more readable for humans.
687 @node Output Variables
688 @section Variables Affecting Output
689 @cindex output-controlling variables
691 @defvar standard-output
692 The value of this variable is the default output stream---the stream
693 that print functions use when the @var{stream} argument is @code{nil}.
694 The default is @code{t}, meaning display in the echo area.
698 If this is non-@code{nil}, that means to print quoted forms using
699 abbreviated reader syntax, e.g.@: @code{(quote foo)} prints as
700 @code{'foo}, and @code{(function foo)} as @code{#'foo}.
703 @defvar print-escape-newlines
704 @cindex @samp{\n} in print
705 @cindex escape characters
706 If this variable is non-@code{nil}, then newline characters in strings
707 are printed as @samp{\n} and formfeeds are printed as @samp{\f}.
708 Normally these characters are printed as actual newlines and formfeeds.
710 This variable affects the print functions @code{prin1} and @code{print}
711 that print with quoting. It does not affect @code{princ}. Here is an
712 example using @code{prin1}:
724 (let ((print-escape-newlines t))
733 In the second expression, the local binding of
734 @code{print-escape-newlines} is in effect during the call to
735 @code{prin1}, but not during the printing of the result.
738 @defvar print-escape-nonascii
739 If this variable is non-@code{nil}, then unibyte non-@acronym{ASCII}
740 characters in strings are unconditionally printed as backslash sequences
741 by the print functions @code{prin1} and @code{print} that print with
744 Those functions also use backslash sequences for unibyte non-@acronym{ASCII}
745 characters, regardless of the value of this variable, when the output
746 stream is a multibyte buffer or a marker pointing into one.
749 @defvar print-escape-multibyte
750 If this variable is non-@code{nil}, then multibyte non-@acronym{ASCII}
751 characters in strings are unconditionally printed as backslash sequences
752 by the print functions @code{prin1} and @code{print} that print with
755 Those functions also use backslash sequences for multibyte
756 non-@acronym{ASCII} characters, regardless of the value of this variable,
757 when the output stream is a unibyte buffer or a marker pointing into
762 @cindex printing limits
763 The value of this variable is the maximum number of elements to print in
764 any list, vector or bool-vector. If an object being printed has more
765 than this many elements, it is abbreviated with an ellipsis.
767 If the value is @code{nil} (the default), then there is no limit.
771 (setq print-length 2)
783 The value of this variable is the maximum depth of nesting of
784 parentheses and brackets when printed. Any list or vector at a depth
785 exceeding this limit is abbreviated with an ellipsis. A value of
786 @code{nil} (which is the default) means no limit.
789 @defopt eval-expression-print-length
790 @defoptx eval-expression-print-level
791 These are the values for @code{print-length} and @code{print-level}
792 used by @code{eval-expression}, and thus, indirectly, by many
793 interactive evaluation commands (@pxref{Lisp Eval,, Evaluating
794 Emacs-Lisp Expressions, emacs, The GNU Emacs Manual}).
797 These variables are used for detecting and reporting circular
798 and shared structure:
801 If non-@code{nil}, this variable enables detection of circular and
802 shared structure in printing. @xref{Circular Objects}.
806 If non-@code{nil}, this variable enables detection of uninterned symbols
807 (@pxref{Creating Symbols}) in printing. When this is enabled,
808 uninterned symbols print with the prefix @samp{#:}, which tells the Lisp
809 reader to produce an uninterned symbol.
812 @defvar print-continuous-numbering
813 If non-@code{nil}, that means number continuously across print calls.
814 This affects the numbers printed for @samp{#@var{n}=} labels and
815 @samp{#@var{m}#} references.
817 Don't set this variable with @code{setq}; you should only bind it
818 temporarily to @code{t} with @code{let}. When you do that, you should
819 also bind @code{print-number-table} to @code{nil}.
822 @defvar print-number-table
823 This variable holds a vector used internally by printing to implement
824 the @code{print-circle} feature. You should not use it except
825 to bind it to @code{nil} when you bind @code{print-continuous-numbering}.
828 @defvar float-output-format
829 This variable specifies how to print floating point numbers. Its
830 default value is @code{nil}, meaning use the shortest output
831 that represents the number without losing information.
833 To control output format more precisely, you can put a string in this
834 variable. The string should hold a @samp{%}-specification to be used
835 in the C function @code{sprintf}. For further restrictions on what
836 you can use, see the variable's documentation string.