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 are @code{a}
54 However, these two operations are not precisely inverses. There are
55 two 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.
72 @section Input Streams
73 @cindex stream (for reading)
76 Most of the Lisp functions for reading text take an @dfn{input stream}
77 as an argument. The input stream specifies where or how to get the
78 characters of the text to be read. Here are the possible types of input
83 @cindex buffer input stream
84 The input characters are read from @var{buffer}, starting with the
85 character directly after point. Point advances as characters are read.
88 @cindex marker input stream
89 The input characters are read from the buffer that @var{marker} is in,
90 starting with the character directly after the marker. The marker
91 position advances as characters are read. The value of point in the
92 buffer has no effect when the stream is a marker.
95 @cindex string input stream
96 The input characters are taken from @var{string}, starting at the first
97 character in the string and using as many characters as required.
100 @cindex function input stream
101 The input characters are generated by @var{function}, one character per
102 call. Normally @var{function} is called with no arguments, and should
106 Occasionally @var{function} is called with one argument (always a
107 character). When that happens, @var{function} should save the argument
108 and arrange to return it on the next call. This is called
109 @dfn{unreading} the character; it happens when the Lisp reader reads one
110 character too many and wants to ``put it back where it came from''.
113 @cindex @code{t} input stream
114 @code{t} used as a stream means that the input is read from the
115 minibuffer. In fact, the minibuffer is invoked once and the text
116 given by the user is made into a string that is then used as the
120 @cindex @code{nil} input stream
121 @code{nil} supplied as an input stream means to use the value of
122 @code{standard-input} instead; that value is the @dfn{default input
123 stream}, and must be a non-@code{nil} input stream.
126 A symbol as input stream is equivalent to the symbol's function
130 Here is an example of reading from a stream which is a buffer, showing
131 where point is located before and after:
135 ---------- Buffer: foo ----------
136 This@point{} is the contents of foo.
137 ---------- Buffer: foo ----------
141 (read (get-buffer "foo"))
145 (read (get-buffer "foo"))
150 ---------- Buffer: foo ----------
151 This is the@point{} contents of foo.
152 ---------- Buffer: foo ----------
157 Note that the first read skips a space at the beginning of the buffer.
158 Reading skips any amount of whitespace preceding the significant text.
160 In Emacs 18, reading a symbol discarded the delimiter terminating the
161 symbol. Thus, point would end up at the beginning of @samp{contents}
162 rather than after @samp{the}. The Emacs 19 behavior is superior because
163 it correctly handles input such as @samp{bar(foo)}, where the delimiter
164 that ends one object is needed as the beginning of another object.
166 Here is an example of reading from a stream that is a marker,
167 initialized to point at the beginning of the buffer shown. The value
168 read is the symbol @code{This}.
173 ---------- Buffer: foo ----------
174 This is the contents of foo.
175 ---------- Buffer: foo ----------
179 (setq m (set-marker (make-marker) 1 (get-buffer "foo")))
180 @result{} #<marker at 1 in foo>
188 @result{} #<marker at 6 in foo> ;; @r{After the first space.}
192 Here we read from the contents of a string:
196 (read "(When in) the course")
201 The following example reads from the minibuffer. The
202 prompt is: @w{@samp{Lisp expression: }}. (That is always the prompt
203 used when you read from the stream @code{t}.) The user's input is shown
204 following the prompt.
210 ---------- Buffer: Minibuffer ----------
211 Lisp expression: @kbd{23 @key{RET}}
212 ---------- Buffer: Minibuffer ----------
216 Finally, here is an example of a stream that is a function, named
217 @code{useless-stream}. Before we use the stream, we initialize the
218 variable @code{useless-list} to a list of characters. Then each call to
219 the function @code{useless-stream} obtains the next characters in the list
220 or unreads a character by adding it to the front of the list.
224 (setq useless-list (append "XY()" nil))
225 @result{} (88 89 40 41)
229 (defun useless-stream (&optional unread)
231 (setq useless-list (cons unread useless-list))
232 (prog1 (car useless-list)
233 (setq useless-list (cdr useless-list)))))
234 @result{} useless-stream
239 Now we read using the stream thus constructed:
243 (read 'useless-stream)
254 Note that the close parenthesis remains in the list. The reader has
255 read it, discovered that it ended the input, and unread it. Another
256 attempt to read from the stream at this point would get an error due to
257 the unmatched close parenthesis.
260 This function is used internally as an input stream to read from the
261 input file opened by the function @code{load}. Don't use this function
265 @node Input Functions
266 @section Input Functions
268 This section describes the Lisp functions and variables that pertain
271 In the functions below, @var{stream} stands for an input stream (see
272 the previous section). If @var{stream} is @code{nil} or omitted, it
273 defaults to the value of @code{standard-input}.
276 An @code{end-of-file} error is signaled if reading encounters an
277 unterminated list, vector or string.
279 @defun read &optional stream
280 This function reads one textual Lisp expression from @var{stream},
281 returning it as a Lisp object. This is the basic Lisp input function.
284 @defun read-from-string string &optional start end
285 @cindex string to object
286 This function reads the first textual Lisp expression from the text in
287 @var{string}. It returns a cons cell whose @sc{car} is that expression,
288 and whose @sc{cdr} is an integer giving the position of the next
289 remaining character in the string (i.e., the first one not read).
291 If @var{start} is supplied, then reading begins at index @var{start} in the
292 string (where the first character is at index 0). If @var{end} is also
293 supplied, then reading stops at that index as if the rest of the string
300 (read-from-string "(setq x 55) (setq y 5)")
301 @result{} ((setq x 55) . 11)
304 (read-from-string "\"A short string\"")
305 @result{} ("A short string" . 16)
309 ;; @r{Read starting at the first character.}
310 (read-from-string "(list 112)" 0)
311 @result{} ((list 112) . 10)
314 ;; @r{Read starting at the second character.}
315 (read-from-string "(list 112)" 1)
319 ;; @r{Read starting at the seventh character,}
320 ;; @r{and stopping at the ninth.}
321 (read-from-string "(list 112)" 6 8)
327 @defvar standard-input
328 This variable holds the default input stream---the stream that
329 @code{read} uses when the @var{stream} argument is @code{nil}.
333 @section Output Streams
334 @cindex stream (for printing)
335 @cindex output stream
337 An output stream specifies what to do with the characters produced
338 by printing. Most print functions accept an output stream as an
339 optional argument. Here are the possible types of output stream:
343 @cindex buffer output stream
344 The output characters are inserted into @var{buffer} at point.
345 Point advances as characters are inserted.
348 @cindex marker output stream
349 The output characters are inserted into the buffer that @var{marker}
350 points into, at the marker position. The position advances as
351 characters are inserted. The value of point in the buffer has no effect
352 on printing when the stream is a marker.
355 @cindex function output stream
356 The output characters are passed to @var{function}, which is responsible
357 for storing them away. It is called with a single character as
358 argument, as many times as there are characters to be output, and is
359 free to do anything at all with the characters it receives.
362 @cindex @code{t} output stream
363 The output characters are displayed in the echo area.
366 @cindex @code{nil} output stream
367 @code{nil} specified as an output stream means to the value of
368 @code{standard-output} instead; that value is the @dfn{default output
369 stream}, and must be a non-@code{nil} output stream.
372 A symbol as output stream is equivalent to the symbol's function
376 Here is an example of a buffer used as an output stream. Point is
377 initially located as shown immediately before the @samp{h} in
378 @samp{the}. At the end, point is located directly before that same
381 @cindex print example
384 ---------- Buffer: foo ----------
385 This is t@point{}he contents of foo.
386 ---------- Buffer: foo ----------
389 (print "This is the output" (get-buffer "foo"))
390 @result{} "This is the output"
393 ---------- Buffer: foo ----------
396 @point{}he contents of foo.
397 ---------- Buffer: foo ----------
401 Now we show a use of a marker as an output stream. Initially, the
402 marker points in buffer @code{foo}, between the @samp{t} and the
403 @samp{h} in the word @samp{the}. At the end, the marker has been
404 advanced over the inserted text so that it still points before the same
405 @samp{h}. Note that the location of point, shown in the usual fashion,
410 ---------- Buffer: foo ----------
411 "This is the @point{}output"
412 ---------- Buffer: foo ----------
417 @result{} #<marker at 11 in foo>
421 (print "More output for foo." m)
422 @result{} "More output for foo."
426 ---------- Buffer: foo ----------
428 "More output for foo."
430 ---------- Buffer: foo ----------
435 @result{} #<marker at 35 in foo>
439 The following example shows output to the echo area:
443 (print "Echo Area output" t)
444 @result{} "Echo Area output"
445 ---------- Echo Area ----------
447 ---------- Echo Area ----------
451 Finally, we show the use of a function as an output stream. The
452 function @code{eat-output} takes each character that it is given and
453 conses it onto the front of the list @code{last-output} (@pxref{Building
454 Lists}). At the end, the list contains all the characters output, but
459 (setq last-output nil)
464 (defun eat-output (c)
465 (setq last-output (cons c last-output)))
470 (print "This is the output" 'eat-output)
471 @result{} "This is the output"
476 @result{} (10 34 116 117 112 116 117 111 32 101 104
477 116 32 115 105 32 115 105 104 84 34 10)
482 Now we can put the output in the proper order by reversing the list:
486 (concat (nreverse last-output))
488 \"This is the output\"
493 @node Output Functions
494 @section Output Functions
496 This section describes the Lisp functions for printing Lisp objects.
498 @cindex @samp{"} in printing
499 @cindex @samp{\} in printing
500 @cindex quoting characters in printing
501 @cindex escape characters in printing
502 Some of the Emacs printing functions add quoting characters to the
503 output when necessary so that it can be read properly. The quoting
504 characters used are @samp{"} and @samp{\}; they distinguish strings from
505 symbols, and prevent punctuation characters in strings and symbols from
506 being taken as delimiters. @xref{Printed Representation}, for full
507 details. You specify quoting or no quoting by the choice of printing
510 If the text is to be read back into Lisp, then it is best to print
511 with quoting characters to avoid ambiguity. Likewise, if the purpose is
512 to describe a Lisp object clearly for a Lisp programmer. However, if
513 the purpose of the output is to look nice for humans, then it is better
514 to print without quoting.
516 Printing a self-referent Lisp object requires an infinite amount of
517 text. In certain cases, trying to produce this text leads to a stack
518 overflow. Emacs detects such recursion and prints @samp{#@var{level}}
519 instead of recursively printing an object already being printed. For
520 example, here @samp{#0} indicates a recursive reference to the object at
521 level 0 of the current print operation:
524 (setq foo (list nil))
530 In the functions below, @var{stream} stands for an output stream.
531 (See the previous section for a description of output streams.) If
532 @var{stream} is @code{nil} or omitted, it defaults to the value of
533 @code{standard-output}.
535 @defun print object &optional stream
537 The @code{print} function is a convenient way of printing. It outputs
538 the printed representation of @var{object} to @var{stream}, printing in
539 addition one newline before @var{object} and another after it. Quoting
540 characters are used. @code{print} returns @var{object}. For example:
544 (progn (print 'The\ cat\ in)
546 (print " came back"))
548 @print{} The\ cat\ in
552 @print{} " came back"
554 @result{} " came back"
559 @defun prin1 object &optional stream
560 This function outputs the printed representation of @var{object} to
561 @var{stream}. It does not print any spaces or newlines to separate
562 output as @code{print} does, but it does use quoting characters just
563 like @code{print}. It returns @var{object}.
567 (progn (prin1 'The\ cat\ in)
569 (prin1 " came back"))
570 @print{} The\ cat\ in"the hat"" came back"
571 @result{} " came back"
576 @defun princ object &optional stream
577 This function outputs the printed representation of @var{object} to
578 @var{stream}. It returns @var{object}.
580 This function is intended to produce output that is readable by people,
581 not by @code{read}, so it doesn't insert quoting characters and doesn't
582 put double-quotes around the contents of strings. It does not add any
583 spacing between calls.
589 (princ " in the \"hat\""))
590 @print{} The cat in the "hat"
591 @result{} " in the \"hat\""
596 @defun terpri &optional stream
597 @cindex newline in print
598 This function outputs a newline to @var{stream}. The name stands
599 for ``terminate print''.
602 @defun write-char character &optional stream
603 This function outputs @var{character} to @var{stream}. It returns
607 @defun prin1-to-string object &optional noescape
608 @cindex object to string
609 This function returns a string containing the text that @code{prin1}
610 would have printed for the same argument.
614 (prin1-to-string 'foo)
618 (prin1-to-string (mark-marker))
619 @result{} "#<marker at 2773 in strings.texi>"
623 If @var{noescape} is non-@code{nil}, that inhibits use of quoting
624 characters in the output. (This argument is supported in Emacs versions
629 (prin1-to-string "foo")
633 (prin1-to-string "foo" t)
638 See @code{format}, in @ref{String Conversion}, for other ways to obtain
639 the printed representation of a Lisp object as a string.
642 @node Output Variables
643 @section Variables Affecting Output
645 @defvar standard-output
646 The value of this variable is the default output stream---the stream
647 that print functions use when the @var{stream} argument is @code{nil}.
650 @defvar print-escape-newlines
651 @cindex @samp{\n} in print
652 @cindex escape characters
653 If this variable is non-@code{nil}, then newline characters in strings
654 are printed as @samp{\n} and formfeeds are printed as @samp{\f}.
655 Normally these characters are printed as actual newlines and formfeeds.
657 This variable affects the print functions @code{prin1} and @code{print},
658 as well as everything that uses them. It does not affect @code{princ}.
659 Here is an example using @code{prin1}:
671 (let ((print-escape-newlines t))
680 In the second expression, the local binding of
681 @code{print-escape-newlines} is in effect during the call to
682 @code{prin1}, but not during the printing of the result.
686 @cindex printing limits
687 The value of this variable is the maximum number of elements of a list
688 that will be printed. If a list being printed has more than this many
689 elements, then it is abbreviated with an ellipsis.
691 If the value is @code{nil} (the default), then there is no limit.
695 (setq print-length 2)
707 The value of this variable is the maximum depth of nesting of
708 parentheses that will be printed. Any list or vector at a depth
709 exceeding this limit is abbreviated with an ellipsis. A value of
710 @code{nil} (which is the default) means no limit.
712 This variable exists in version 19 and later versions.