2 @c This is part of the GNU Emacs Lisp Reference Manual.
3 @c Copyright (C) 1990, 1991, 1992, 1993, 1994 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 printed representation. Printing
42 the cons cell described 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 inverses. There are
55 three kinds of exceptions:
59 Printing can produce text that cannot be read. For example, buffers,
60 windows, frames, subprocesses and markers print into 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}, one character per
106 call. Normally @var{function} is called with no arguments, and should
110 Occasionally @var{function} is called with one argument (always a
111 character). When that happens, @var{function} should save the argument
112 and arrange to return it on the next call. This is called
113 @dfn{unreading} the character; it happens when the Lisp reader reads one
114 character too many and wants to ``put it back where it came from''.
117 @cindex @code{t} input stream
118 @code{t} used as a stream means that the input is read from the
119 minibuffer. In fact, the minibuffer is invoked once and the text
120 given by the user is made into a string that is then used as the
124 @cindex @code{nil} input stream
125 @code{nil} supplied as an input stream means to use the value of
126 @code{standard-input} instead; that value is the @dfn{default input
127 stream}, and must be a non-@code{nil} input stream.
130 A symbol as input stream is equivalent to the symbol's function
134 Here is an example of reading from a stream that is a buffer, showing
135 where point is located before and after:
139 ---------- Buffer: foo ----------
140 This@point{} is the contents of foo.
141 ---------- Buffer: foo ----------
145 (read (get-buffer "foo"))
149 (read (get-buffer "foo"))
154 ---------- Buffer: foo ----------
155 This is the@point{} contents of foo.
156 ---------- Buffer: foo ----------
161 Note that the first read skips a space. Reading skips any amount of
162 whitespace preceding the significant text.
164 In Emacs 18, reading a symbol discarded the delimiter terminating the
165 symbol. Thus, point would end up at the beginning of @samp{contents}
166 rather than after @samp{the}. The Emacs 19 behavior is superior because
167 it correctly handles input such as @samp{bar(foo)}, where the
168 open-parenthesis that ends one object is needed as the beginning of
171 Here is an example of reading from a stream that is a marker,
172 initially positioned at the beginning of the buffer shown. The value
173 read is the symbol @code{This}.
178 ---------- Buffer: foo ----------
179 This is the contents of foo.
180 ---------- Buffer: foo ----------
184 (setq m (set-marker (make-marker) 1 (get-buffer "foo")))
185 @result{} #<marker at 1 in foo>
193 @result{} #<marker at 5 in foo> ;; @r{Before the first space.}
197 Here we read from the contents of a string:
201 (read "(When in) the course")
206 The following example reads from the minibuffer. The
207 prompt is: @w{@samp{Lisp expression: }}. (That is always the prompt
208 used when you read from the stream @code{t}.) The user's input is shown
209 following the prompt.
215 ---------- Buffer: Minibuffer ----------
216 Lisp expression: @kbd{23 @key{RET}}
217 ---------- Buffer: Minibuffer ----------
221 Finally, here is an example of a stream that is a function, named
222 @code{useless-stream}. Before we use the stream, we initialize the
223 variable @code{useless-list} to a list of characters. Then each call to
224 the function @code{useless-stream} obtains the next character in the list
225 or unreads a character by adding it to the front of the list.
229 (setq useless-list (append "XY()" nil))
230 @result{} (88 89 40 41)
234 (defun useless-stream (&optional unread)
236 (setq useless-list (cons unread useless-list))
237 (prog1 (car useless-list)
238 (setq useless-list (cdr useless-list)))))
239 @result{} useless-stream
244 Now we read using the stream thus constructed:
248 (read 'useless-stream)
259 Note that the open and close parentheses remains in the list. The Lisp
260 reader encountered the open parenthesis, decided that it ended the
261 input, and unread it. Another attempt to read from the stream at this
262 point would read @samp{()} and return @code{nil}.
265 This function is used internally as an input stream to read from the
266 input file opened by the function @code{load}. Don't use this function
270 @node Input Functions
271 @section Input Functions
273 This section describes the Lisp functions and variables that pertain
276 In the functions below, @var{stream} stands for an input stream (see
277 the previous section). If @var{stream} is @code{nil} or omitted, it
278 defaults to the value of @code{standard-input}.
281 An @code{end-of-file} error is signaled if reading encounters an
282 unterminated list, vector, or string.
284 @defun read &optional stream
285 This function reads one textual Lisp expression from @var{stream},
286 returning it as a Lisp object. This is the basic Lisp input function.
289 @defun read-from-string string &optional start end
290 @cindex string to object
291 This function reads the first textual Lisp expression from the text in
292 @var{string}. It returns a cons cell whose @sc{car} is that expression,
293 and whose @sc{cdr} is an integer giving the position of the next
294 remaining character in the string (i.e., the first one not read).
296 If @var{start} is supplied, then reading begins at index @var{start} in
297 the string (where the first character is at index 0). If @var{end} is
298 also supplied, then reading stops just before that index, as if the rest
299 of the string were not there.
305 (read-from-string "(setq x 55) (setq y 5)")
306 @result{} ((setq x 55) . 11)
309 (read-from-string "\"A short string\"")
310 @result{} ("A short string" . 16)
314 ;; @r{Read starting at the first character.}
315 (read-from-string "(list 112)" 0)
316 @result{} ((list 112) . 10)
319 ;; @r{Read starting at the second character.}
320 (read-from-string "(list 112)" 1)
324 ;; @r{Read starting at the seventh character,}
325 ;; @r{and stopping at the ninth.}
326 (read-from-string "(list 112)" 6 8)
332 @defvar standard-input
333 This variable holds the default input stream---the stream that
334 @code{read} uses when the @var{stream} argument is @code{nil}.
338 @section Output Streams
339 @cindex stream (for printing)
340 @cindex output stream
342 An output stream specifies what to do with the characters produced
343 by printing. Most print functions accept an output stream as an
344 optional argument. Here are the possible types of output stream:
348 @cindex buffer output stream
349 The output characters are inserted into @var{buffer} at point.
350 Point advances as characters are inserted.
353 @cindex marker output stream
354 The output characters are inserted into the buffer that @var{marker}
355 points into, at the marker position. The marker position advances as
356 characters are inserted. The value of point in the buffer has no effect
357 on printing when the stream is a marker.
360 @cindex function output stream
361 The output characters are passed to @var{function}, which is responsible
362 for storing them away. It is called with a single character as
363 argument, as many times as there are characters to be output, and is
364 free to do anything at all with the characters it receives.
367 @cindex @code{t} output stream
368 The output characters are displayed in the echo area.
371 @cindex @code{nil} output stream
372 @code{nil} specified as an output stream means to the value of
373 @code{standard-output} instead; that value is the @dfn{default output
374 stream}, and must be a non-@code{nil} output stream.
377 A symbol as output stream is equivalent to the symbol's function
381 Many of the valid output streams are also valid as input streams. The
382 difference between input and output streams is therefore mostly one of
383 how you use a Lisp object, not a distinction of types of object.
385 Here is an example of a buffer used as an output stream. Point is
386 initially located as shown immediately before the @samp{h} in
387 @samp{the}. At the end, point is located directly before that same
390 @cindex print example
393 (setq m (set-marker (make-marker) 10 (get-buffer "foo")))
394 @result{} #<marker at 10 in foo>
398 ---------- Buffer: foo ----------
399 This is t@point{}he contents of foo.
400 ---------- Buffer: foo ----------
403 (print "This is the output" (get-buffer "foo"))
404 @result{} "This is the output"
408 @result{} #<marker at 32 in foo>
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 ----------
435 @result{} #<marker at 11 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 35 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 objects.
520 @cindex @samp{"} in printing
521 @cindex @samp{\} in printing
522 @cindex quoting characters in printing
523 @cindex escape characters in printing
524 Some of the Emacs printing functions add quoting characters to the
525 output when necessary so that it can be read properly. The quoting
526 characters used are @samp{"} and @samp{\}; they distinguish strings from
527 symbols, and prevent punctuation characters in strings and symbols from
528 being taken as delimiters when reading. @xref{Printed Representation},
529 for full details. You specify quoting or no quoting by the choice of
532 If the text is to be read back into Lisp, then it is best to print
533 with quoting characters to avoid ambiguity. Likewise, if the purpose is
534 to describe a Lisp object clearly for a Lisp programmer. However, if
535 the purpose of the output is to look nice for humans, then it is better
536 to print without quoting.
538 Printing a self-referent Lisp object requires an infinite amount of
539 text. In certain cases, trying to produce this text leads to a stack
540 overflow. Emacs detects such recursion and prints @samp{#@var{level}}
541 instead of recursively printing an object already being printed. For
542 example, here @samp{#0} indicates a recursive reference to the object at
543 level 0 of the current print operation:
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"
576 @result{} " came back"
581 @defun prin1 object &optional stream
582 This function outputs the printed representation of @var{object} to
583 @var{stream}. It does not print newlines to separate output as
584 @code{print} does, but it does use quoting characters just like
585 @code{print}. It returns @var{object}.
589 (progn (prin1 'The\ cat\ in)
591 (prin1 " came back"))
592 @print{} The\ cat\ in"the hat"" came back"
593 @result{} " came back"
598 @defun princ object &optional stream
599 This function outputs the printed representation of @var{object} to
600 @var{stream}. It returns @var{object}.
602 This function is intended to produce output that is readable by people,
603 not by @code{read}, so it doesn't insert quoting characters and doesn't
604 put double-quotes around the contents of strings. It does not add any
605 spacing between calls.
611 (princ " in the \"hat\""))
612 @print{} The cat in the "hat"
613 @result{} " in the \"hat\""
618 @defun terpri &optional stream
619 @cindex newline in print
620 This function outputs a newline to @var{stream}. The name stands
621 for ``terminate print''.
624 @defun write-char character &optional stream
625 This function outputs @var{character} to @var{stream}. It returns
629 @defun prin1-to-string object &optional noescape
630 @cindex object to string
631 This function returns a string containing the text that @code{prin1}
632 would have printed for the same argument.
636 (prin1-to-string 'foo)
640 (prin1-to-string (mark-marker))
641 @result{} "#<marker at 2773 in strings.texi>"
645 If @var{noescape} is non-@code{nil}, that inhibits use of quoting
646 characters in the output. (This argument is supported in Emacs versions
651 (prin1-to-string "foo")
655 (prin1-to-string "foo" t)
660 See @code{format}, in @ref{String Conversion}, for other ways to obtain
661 the printed representation of a Lisp object as a string.
664 @node Output Variables
665 @section Variables Affecting Output
667 @defvar standard-output
668 The value of this variable is the default output stream---the stream
669 that print functions use when the @var{stream} argument is @code{nil}.
672 @defvar print-escape-newlines
673 @cindex @samp{\n} in print
674 @cindex escape characters
675 If this variable is non-@code{nil}, then newline characters in strings
676 are printed as @samp{\n} and formfeeds are printed as @samp{\f}.
677 Normally these characters are printed as actual newlines and formfeeds.
679 This variable affects the print functions @code{prin1} and @code{print},
680 as well as everything that uses them. It does not affect @code{princ}.
681 Here is an example using @code{prin1}:
693 (let ((print-escape-newlines t))
702 In the second expression, the local binding of
703 @code{print-escape-newlines} is in effect during the call to
704 @code{prin1}, but not during the printing of the result.
708 @cindex printing limits
709 The value of this variable is the maximum number of elements of a list,
710 vector or bitvector that will be printed. If an object being printed has
711 more than this many elements, it is abbreviated with an ellipsis.
713 If the value is @code{nil} (the default), then there is no limit.
717 (setq print-length 2)
729 The value of this variable is the maximum depth of nesting of
730 parentheses and brackets when printed. Any list or vector at a depth
731 exceeding this limit is abbreviated with an ellipsis. A value of
732 @code{nil} (which is the default) means no limit.
734 This variable exists in version 19 and later versions.