2 @c This is part of the GNU Emacs Lisp Reference Manual.
3 @c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1998, 1999, 2001, 2002,
4 @c 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc.
5 @c See the file elisp.texi for copying conditions.
6 @setfilename ../../info/streams
7 @node Read and Print, Minibuffers, Debugging, Top
8 @comment node-name, next, previous, up
9 @chapter Reading and Printing Lisp Objects
11 @dfn{Printing} and @dfn{reading} are the operations of converting Lisp
12 objects to textual form and vice versa. They use the printed
13 representations and read syntax described in @ref{Lisp Data Types}.
15 This chapter describes the Lisp functions for reading and printing.
16 It also describes @dfn{streams}, which specify where to get the text (if
17 reading) or where to put it (if printing).
20 * Streams Intro:: Overview of streams, reading and printing.
21 * Input Streams:: Various data types that can be used as input streams.
22 * Input Functions:: Functions to read Lisp objects from text.
23 * Output Streams:: Various data types that can be used as output streams.
24 * Output Functions:: Functions to print Lisp objects as text.
25 * Output Variables:: Variables that control what the printing functions do.
29 @section Introduction to Reading and Printing
34 @dfn{Reading} a Lisp object means parsing a Lisp expression in textual
35 form and producing a corresponding Lisp object. This is how Lisp
36 programs get into Lisp from files of Lisp code. We call the text the
37 @dfn{read syntax} of the object. For example, the text @samp{(a .@: 5)}
38 is the read syntax for a cons cell whose @sc{car} is @code{a} and whose
39 @sc{cdr} is the number 5.
41 @dfn{Printing} a Lisp object means producing text that represents that
42 object---converting the object to its @dfn{printed representation}
43 (@pxref{Printed Representation}). Printing the cons cell described
44 above produces the text @samp{(a .@: 5)}.
46 Reading and printing are more or less inverse operations: printing the
47 object that results from reading a given piece of text often produces
48 the same text, and reading the text that results from printing an object
49 usually produces a similar-looking object. For example, printing the
50 symbol @code{foo} produces the text @samp{foo}, and reading that text
51 returns the symbol @code{foo}. Printing a list whose elements are
52 @code{a} and @code{b} produces the text @samp{(a b)}, and reading that
53 text produces a list (but not the same list) with elements @code{a}
56 However, these two operations are not precisely inverse to each other.
57 There are three kinds of exceptions:
61 Printing can produce text that cannot be read. For example, buffers,
62 windows, frames, subprocesses and markers print as text that starts
63 with @samp{#}; if you try to read this text, you get an error. There is
64 no way to read those data types.
67 One object can have multiple textual representations. For example,
68 @samp{1} and @samp{01} represent the same integer, and @samp{(a b)} and
69 @samp{(a .@: (b))} represent the same list. Reading will accept any of
70 the alternatives, but printing must choose one of them.
73 Comments can appear at certain points in the middle of an object's
74 read sequence without affecting the result of reading it.
78 @section Input Streams
79 @cindex stream (for reading)
82 Most of the Lisp functions for reading text take an @dfn{input stream}
83 as an argument. The input stream specifies where or how to get the
84 characters of the text to be read. Here are the possible types of input
89 @cindex buffer input stream
90 The input characters are read from @var{buffer}, starting with the
91 character directly after point. Point advances as characters are read.
94 @cindex marker input stream
95 The input characters are read from the buffer that @var{marker} is in,
96 starting with the character directly after the marker. The marker
97 position advances as characters are read. The value of point in the
98 buffer has no effect when the stream is a marker.
101 @cindex string input stream
102 The input characters are taken from @var{string}, starting at the first
103 character in the string and using as many characters as required.
106 @cindex function input stream
107 The input characters are generated by @var{function}, which must support
112 When it is called with no arguments, it should return the next character.
115 When it is called with one argument (always a character), @var{function}
116 should save the argument and arrange to return it on the next call.
117 This is called @dfn{unreading} the character; it happens when the Lisp
118 reader reads one character too many and wants to ``put it back where it
119 came from.'' In this case, it makes no difference what value
120 @var{function} returns.
124 @cindex @code{t} input stream
125 @code{t} used as a stream means that the input is read from the
126 minibuffer. In fact, the minibuffer is invoked once and the text
127 given by the user is made into a string that is then used as the
128 input stream. If Emacs is running in batch mode, standard input is used
129 instead of the minibuffer. For example,
131 (message "%s" (read t))
133 will read a Lisp expression from standard input and print the result
137 @cindex @code{nil} input stream
138 @code{nil} supplied as an input stream means to use the value of
139 @code{standard-input} instead; that value is the @dfn{default input
140 stream}, and must be a non-@code{nil} input stream.
143 A symbol as input stream is equivalent to the symbol's function
147 Here is an example of reading from a stream that is a buffer, showing
148 where point is located before and after:
152 ---------- Buffer: foo ----------
153 This@point{} is the contents of foo.
154 ---------- Buffer: foo ----------
158 (read (get-buffer "foo"))
162 (read (get-buffer "foo"))
167 ---------- Buffer: foo ----------
168 This is the@point{} contents of foo.
169 ---------- Buffer: foo ----------
174 Note that the first read skips a space. Reading skips any amount of
175 whitespace preceding the significant text.
177 Here is an example of reading from a stream that is a marker,
178 initially positioned at the beginning of the buffer shown. The value
179 read is the symbol @code{This}.
184 ---------- Buffer: foo ----------
185 This is the contents of foo.
186 ---------- Buffer: foo ----------
190 (setq m (set-marker (make-marker) 1 (get-buffer "foo")))
191 @result{} #<marker at 1 in foo>
199 @result{} #<marker at 5 in foo> ;; @r{Before the first space.}
203 Here we read from the contents of a string:
207 (read "(When in) the course")
212 The following example reads from the minibuffer. The
213 prompt is: @w{@samp{Lisp expression: }}. (That is always the prompt
214 used when you read from the stream @code{t}.) The user's input is shown
215 following the prompt.
221 ---------- Buffer: Minibuffer ----------
222 Lisp expression: @kbd{23 @key{RET}}
223 ---------- Buffer: Minibuffer ----------
227 Finally, here is an example of a stream that is a function, named
228 @code{useless-stream}. Before we use the stream, we initialize the
229 variable @code{useless-list} to a list of characters. Then each call to
230 the function @code{useless-stream} obtains the next character in the list
231 or unreads a character by adding it to the front of the list.
235 (setq useless-list (append "XY()" nil))
236 @result{} (88 89 40 41)
240 (defun useless-stream (&optional unread)
242 (setq useless-list (cons unread useless-list))
243 (prog1 (car useless-list)
244 (setq useless-list (cdr useless-list)))))
245 @result{} useless-stream
250 Now we read using the stream thus constructed:
254 (read 'useless-stream)
265 Note that the open and close parentheses remain in the list. The Lisp
266 reader encountered the open parenthesis, decided that it ended the
267 input, and unread it. Another attempt to read from the stream at this
268 point would read @samp{()} and return @code{nil}.
271 This function is used internally as an input stream to read from the
272 input file opened by the function @code{load}. Don't use this function
276 @node Input Functions
277 @section Input Functions
279 This section describes the Lisp functions and variables that pertain
282 In the functions below, @var{stream} stands for an input stream (see
283 the previous section). If @var{stream} is @code{nil} or omitted, it
284 defaults to the value of @code{standard-input}.
287 An @code{end-of-file} error is signaled if reading encounters an
288 unterminated list, vector, or string.
290 @defun read &optional stream
291 This function reads one textual Lisp expression from @var{stream},
292 returning it as a Lisp object. This is the basic Lisp input function.
295 @defun read-from-string string &optional start end
296 @cindex string to object
297 This function reads the first textual Lisp expression from the text in
298 @var{string}. It returns a cons cell whose @sc{car} is that expression,
299 and whose @sc{cdr} is an integer giving the position of the next
300 remaining character in the string (i.e., the first one not read).
302 If @var{start} is supplied, then reading begins at index @var{start} in
303 the string (where the first character is at index 0). If you specify
304 @var{end}, then reading is forced to stop just before that index, as if
305 the rest of the string were not there.
311 (read-from-string "(setq x 55) (setq y 5)")
312 @result{} ((setq x 55) . 11)
315 (read-from-string "\"A short string\"")
316 @result{} ("A short string" . 16)
320 ;; @r{Read starting at the first character.}
321 (read-from-string "(list 112)" 0)
322 @result{} ((list 112) . 10)
325 ;; @r{Read starting at the second character.}
326 (read-from-string "(list 112)" 1)
330 ;; @r{Read starting at the seventh character,}
331 ;; @r{and stopping at the ninth.}
332 (read-from-string "(list 112)" 6 8)
338 @defvar standard-input
339 This variable holds the default input stream---the stream that
340 @code{read} uses when the @var{stream} argument is @code{nil}.
341 The default is @code{t}, meaning use the minibuffer.
345 @section Output Streams
346 @cindex stream (for printing)
347 @cindex output stream
349 An output stream specifies what to do with the characters produced
350 by printing. Most print functions accept an output stream as an
351 optional argument. Here are the possible types of output stream:
355 @cindex buffer output stream
356 The output characters are inserted into @var{buffer} at point.
357 Point advances as characters are inserted.
360 @cindex marker output stream
361 The output characters are inserted into the buffer that @var{marker}
362 points into, at the marker position. The marker position advances as
363 characters are inserted. The value of point in the buffer has no effect
364 on printing when the stream is a marker, and this kind of printing
365 does not move point (except that if the marker points at or before the
366 position of point, point advances with the surrounding text, as
370 @cindex function output stream
371 The output characters are passed to @var{function}, which is responsible
372 for storing them away. It is called with a single character as
373 argument, as many times as there are characters to be output, and
374 is responsible for storing the characters wherever you want to put them.
377 @cindex @code{t} output stream
378 The output characters are displayed in the echo area.
381 @cindex @code{nil} output stream
382 @code{nil} specified as an output stream means to use the value of
383 @code{standard-output} instead; that value is the @dfn{default output
384 stream}, and must not be @code{nil}.
387 A symbol as output stream is equivalent to the symbol's function
391 Many of the valid output streams are also valid as input streams. The
392 difference between input and output streams is therefore more a matter
393 of how you use a Lisp object, than of different types of object.
395 Here is an example of a buffer used as an output stream. Point is
396 initially located as shown immediately before the @samp{h} in
397 @samp{the}. At the end, point is located directly before that same
400 @cindex print example
403 ---------- Buffer: foo ----------
404 This is t@point{}he contents of foo.
405 ---------- Buffer: foo ----------
408 (print "This is the output" (get-buffer "foo"))
409 @result{} "This is the output"
412 ---------- Buffer: foo ----------
415 @point{}he contents of foo.
416 ---------- Buffer: foo ----------
420 Now we show a use of a marker as an output stream. Initially, the
421 marker is in buffer @code{foo}, between the @samp{t} and the @samp{h} in
422 the word @samp{the}. At the end, the marker has advanced over the
423 inserted text so that it remains positioned before the same @samp{h}.
424 Note that the location of point, shown in the usual fashion, has no
429 ---------- Buffer: foo ----------
430 This is the @point{}output
431 ---------- Buffer: foo ----------
435 (setq m (copy-marker 10))
436 @result{} #<marker at 10 in foo>
440 (print "More output for foo." m)
441 @result{} "More output for foo."
445 ---------- Buffer: foo ----------
447 "More output for foo."
449 ---------- Buffer: foo ----------
454 @result{} #<marker at 34 in foo>
458 The following example shows output to the echo area:
462 (print "Echo Area output" t)
463 @result{} "Echo Area output"
464 ---------- Echo Area ----------
466 ---------- Echo Area ----------
470 Finally, we show the use of a function as an output stream. The
471 function @code{eat-output} takes each character that it is given and
472 conses it onto the front of the list @code{last-output} (@pxref{Building
473 Lists}). At the end, the list contains all the characters output, but
478 (setq last-output nil)
483 (defun eat-output (c)
484 (setq last-output (cons c last-output)))
489 (print "This is the output" 'eat-output)
490 @result{} "This is the output"
495 @result{} (10 34 116 117 112 116 117 111 32 101 104
496 116 32 115 105 32 115 105 104 84 34 10)
501 Now we can put the output in the proper order by reversing the list:
505 (concat (nreverse last-output))
507 \"This is the output\"
513 Calling @code{concat} converts the list to a string so you can see its
514 contents more clearly.
516 @node Output Functions
517 @section Output Functions
519 This section describes the Lisp functions for printing Lisp
520 objects---converting objects into their printed representation.
522 @cindex @samp{"} in printing
523 @cindex @samp{\} in printing
524 @cindex quoting characters in printing
525 @cindex escape characters in printing
526 Some of the Emacs printing functions add quoting characters to the
527 output when necessary so that it can be read properly. The quoting
528 characters used are @samp{"} and @samp{\}; they distinguish strings from
529 symbols, and prevent punctuation characters in strings and symbols from
530 being taken as delimiters when reading. @xref{Printed Representation},
531 for full details. You specify quoting or no quoting by the choice of
534 If the text is to be read back into Lisp, then you should print with
535 quoting characters to avoid ambiguity. Likewise, if the purpose is to
536 describe a Lisp object clearly for a Lisp programmer. However, if the
537 purpose of the output is to look nice for humans, then it is usually
538 better to print without quoting.
540 Lisp objects can refer to themselves. Printing a self-referential
541 object in the normal way would require an infinite amount of text, and
542 the attempt could cause infinite recursion. Emacs detects such
543 recursion and prints @samp{#@var{level}} instead of recursively printing
544 an object already being printed. For example, here @samp{#0} indicates
545 a recursive reference to the object at level 0 of the current print
549 (setq foo (list nil))
555 In the functions below, @var{stream} stands for an output stream.
556 (See the previous section for a description of output streams.) If
557 @var{stream} is @code{nil} or omitted, it defaults to the value of
558 @code{standard-output}.
560 @defun print object &optional stream
562 The @code{print} function is a convenient way of printing. It outputs
563 the printed representation of @var{object} to @var{stream}, printing in
564 addition one newline before @var{object} and another after it. Quoting
565 characters are used. @code{print} returns @var{object}. For example:
569 (progn (print 'The\ cat\ in)
571 (print " came back"))
573 @print{} The\ cat\ in
577 @print{} " came back"
578 @result{} " came back"
583 @defun prin1 object &optional stream
584 This function outputs the printed representation of @var{object} to
585 @var{stream}. It does not print newlines to separate output as
586 @code{print} does, but it does use quoting characters just like
587 @code{print}. It returns @var{object}.
591 (progn (prin1 'The\ cat\ in)
593 (prin1 " came back"))
594 @print{} The\ cat\ in"the hat"" came back"
595 @result{} " came back"
600 @defun princ object &optional stream
601 This function outputs the printed representation of @var{object} to
602 @var{stream}. It returns @var{object}.
604 This function is intended to produce output that is readable by people,
605 not by @code{read}, so it doesn't insert quoting characters and doesn't
606 put double-quotes around the contents of strings. It does not add any
607 spacing between calls.
613 (princ " in the \"hat\""))
614 @print{} The cat in the "hat"
615 @result{} " in the \"hat\""
620 @defun terpri &optional stream
621 @cindex newline in print
622 This function outputs a newline to @var{stream}. The name stands
623 for ``terminate print.''
626 @defun write-char character &optional stream
627 This function outputs @var{character} to @var{stream}. It returns
631 @defun prin1-to-string object &optional noescape
632 @cindex object to string
633 This function returns a string containing the text that @code{prin1}
634 would have printed for the same argument.
638 (prin1-to-string 'foo)
642 (prin1-to-string (mark-marker))
643 @result{} "#<marker at 2773 in strings.texi>"
647 If @var{noescape} is non-@code{nil}, that inhibits use of quoting
648 characters in the output. (This argument is supported in Emacs versions
653 (prin1-to-string "foo")
657 (prin1-to-string "foo" t)
662 See @code{format}, in @ref{Formatting Strings}, for other ways to obtain
663 the printed representation of a Lisp object as a string.
666 @defmac with-output-to-string body@dots{}
667 This macro executes the @var{body} forms with @code{standard-output} set
668 up to feed output into a string. Then it returns that string.
670 For example, if the current buffer name is @samp{foo},
673 (with-output-to-string
674 (princ "The buffer is ")
675 (princ (buffer-name)))
679 returns @code{"The buffer is foo"}.
682 @node Output Variables
683 @section Variables Affecting Output
684 @cindex output-controlling variables
686 @defvar standard-output
687 The value of this variable is the default output stream---the stream
688 that print functions use when the @var{stream} argument is @code{nil}.
689 The default is @code{t}, meaning display in the echo area.
693 If this is non-@code{nil}, that means to print quoted forms using
694 abbreviated reader syntax. @code{(quote foo)} prints as @code{'foo},
695 @code{(function foo)} as @code{#'foo}, and backquoted forms print
696 using modern backquote syntax.
699 @defvar print-escape-newlines
700 @cindex @samp{\n} in print
701 @cindex escape characters
702 If this variable is non-@code{nil}, then newline characters in strings
703 are printed as @samp{\n} and formfeeds are printed as @samp{\f}.
704 Normally these characters are printed as actual newlines and formfeeds.
706 This variable affects the print functions @code{prin1} and @code{print}
707 that print with quoting. It does not affect @code{princ}. Here is an
708 example using @code{prin1}:
720 (let ((print-escape-newlines t))
729 In the second expression, the local binding of
730 @code{print-escape-newlines} is in effect during the call to
731 @code{prin1}, but not during the printing of the result.
734 @defvar print-escape-nonascii
735 If this variable is non-@code{nil}, then unibyte non-@acronym{ASCII}
736 characters in strings are unconditionally printed as backslash sequences
737 by the print functions @code{prin1} and @code{print} that print with
740 Those functions also use backslash sequences for unibyte non-@acronym{ASCII}
741 characters, regardless of the value of this variable, when the output
742 stream is a multibyte buffer or a marker pointing into one.
745 @defvar print-escape-multibyte
746 If this variable is non-@code{nil}, then multibyte non-@acronym{ASCII}
747 characters in strings are unconditionally printed as backslash sequences
748 by the print functions @code{prin1} and @code{print} that print with
751 Those functions also use backslash sequences for multibyte
752 non-@acronym{ASCII} characters, regardless of the value of this variable,
753 when the output stream is a unibyte buffer or a marker pointing into
758 @cindex printing limits
759 The value of this variable is the maximum number of elements to print in
760 any list, vector or bool-vector. If an object being printed has more
761 than this many elements, it is abbreviated with an ellipsis.
763 If the value is @code{nil} (the default), then there is no limit.
767 (setq print-length 2)
779 The value of this variable is the maximum depth of nesting of
780 parentheses and brackets when printed. Any list or vector at a depth
781 exceeding this limit is abbreviated with an ellipsis. A value of
782 @code{nil} (which is the default) means no limit.
785 @defopt eval-expression-print-length
786 @defoptx eval-expression-print-level
787 These are the values for @code{print-length} and @code{print-level}
788 used by @code{eval-expression}, and thus, indirectly, by many
789 interactive evaluation commands (@pxref{Lisp Eval,, Evaluating
790 Emacs-Lisp Expressions, emacs, The GNU Emacs Manual}).
793 These variables are used for detecting and reporting circular
794 and shared structure:
797 If non-@code{nil}, this variable enables detection of circular
798 and shared structure in printing.
802 If non-@code{nil}, this variable enables detection of uninterned symbols
803 (@pxref{Creating Symbols}) in printing. When this is enabled,
804 uninterned symbols print with the prefix @samp{#:}, which tells the Lisp
805 reader to produce an uninterned symbol.
808 @defvar print-continuous-numbering
809 If non-@code{nil}, that means number continuously across print calls.
810 This affects the numbers printed for @samp{#@var{n}=} labels and
811 @samp{#@var{m}#} references.
813 Don't set this variable with @code{setq}; you should only bind it
814 temporarily to @code{t} with @code{let}. When you do that, you should
815 also bind @code{print-number-table} to @code{nil}.
818 @defvar print-number-table
819 This variable holds a vector used internally by printing to implement
820 the @code{print-circle} feature. You should not use it except
821 to bind it to @code{nil} when you bind @code{print-continuous-numbering}.
824 @defvar float-output-format
825 This variable specifies how to print floating point numbers. Its
826 default value is @code{nil}, meaning use the shortest output
827 that represents the number without losing information.
829 To control output format more precisely, you can put a string in this
830 variable. The string should hold a @samp{%}-specification to be used
831 in the C function @code{sprintf}. For further restrictions on what
832 you can use, see the variable's documentation string.
836 arch-tag: 07636b8c-c4e3-4735-9e06-2e864320b434