Backport 2012-05-02T11:33:49Z!lekktu@gmail.com from trunk
[bpt/emacs.git] / doc / lispref / streams.texi
CommitLineData
b8d4c8d0
GM
1@c -*-texinfo-*-
2@c This is part of the GNU Emacs Lisp Reference Manual.
acaf905b 3@c Copyright (C) 1990-1994, 1998-1999, 2001-2012 Free Software Foundation, Inc.
b8d4c8d0 4@c See the file elisp.texi for copying conditions.
6336d8c3 5@setfilename ../../info/streams
b8d4c8d0
GM
6@node Read and Print, Minibuffers, Debugging, Top
7@comment node-name, next, previous, up
8@chapter Reading and Printing Lisp Objects
9
10 @dfn{Printing} and @dfn{reading} are the operations of converting Lisp
11objects to textual form and vice versa. They use the printed
12representations and read syntax described in @ref{Lisp Data Types}.
13
14 This chapter describes the Lisp functions for reading and printing.
15It also describes @dfn{streams}, which specify where to get the text (if
16reading) or where to put it (if printing).
17
18@menu
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.
25@end menu
26
27@node Streams Intro
28@section Introduction to Reading and Printing
29@cindex Lisp reader
30@cindex printing
31@cindex reading
32
33 @dfn{Reading} a Lisp object means parsing a Lisp expression in textual
34form and producing a corresponding Lisp object. This is how Lisp
35programs 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)}
37is the read syntax for a cons cell whose @sc{car} is @code{a} and whose
38@sc{cdr} is the number 5.
39
40 @dfn{Printing} a Lisp object means producing text that represents that
41object---converting the object to its @dfn{printed representation}
42(@pxref{Printed Representation}). Printing the cons cell described
43above produces the text @samp{(a .@: 5)}.
44
45 Reading and printing are more or less inverse operations: printing the
46object that results from reading a given piece of text often produces
47the same text, and reading the text that results from printing an object
48usually produces a similar-looking object. For example, printing the
49symbol @code{foo} produces the text @samp{foo}, and reading that text
50returns 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
52text produces a list (but not the same list) with elements @code{a}
53and @code{b}.
54
55 However, these two operations are not precisely inverse to each other.
56There are three kinds of exceptions:
57
58@itemize @bullet
59@item
60Printing can produce text that cannot be read. For example, buffers,
61windows, frames, subprocesses and markers print as text that starts
62with @samp{#}; if you try to read this text, you get an error. There is
63no way to read those data types.
64
65@item
66One 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
69the alternatives, but printing must choose one of them.
70
71@item
72Comments can appear at certain points in the middle of an object's
73read sequence without affecting the result of reading it.
74@end itemize
75
76@node Input Streams
77@section Input Streams
78@cindex stream (for reading)
79@cindex input stream
80
81 Most of the Lisp functions for reading text take an @dfn{input stream}
82as an argument. The input stream specifies where or how to get the
83characters of the text to be read. Here are the possible types of input
84stream:
85
86@table @asis
87@item @var{buffer}
88@cindex buffer input stream
89The input characters are read from @var{buffer}, starting with the
90character directly after point. Point advances as characters are read.
91
92@item @var{marker}
93@cindex marker input stream
94The input characters are read from the buffer that @var{marker} is in,
95starting with the character directly after the marker. The marker
96position advances as characters are read. The value of point in the
97buffer has no effect when the stream is a marker.
98
99@item @var{string}
100@cindex string input stream
101The input characters are taken from @var{string}, starting at the first
102character in the string and using as many characters as required.
103
104@item @var{function}
105@cindex function input stream
106The input characters are generated by @var{function}, which must support
107two kinds of calls:
108
109@itemize @bullet
110@item
111When it is called with no arguments, it should return the next character.
112
113@item
114When it is called with one argument (always a character), @var{function}
115should save the argument and arrange to return it on the next call.
116This is called @dfn{unreading} the character; it happens when the Lisp
117reader reads one character too many and wants to ``put it back where it
16152b76 118came from''. In this case, it makes no difference what value
b8d4c8d0
GM
119@var{function} returns.
120@end itemize
121
122@item @code{t}
123@cindex @code{t} input stream
124@code{t} used as a stream means that the input is read from the
125minibuffer. In fact, the minibuffer is invoked once and the text
126given by the user is made into a string that is then used as the
127input stream. If Emacs is running in batch mode, standard input is used
128instead of the minibuffer. For example,
129@example
130(message "%s" (read t))
131@end example
132will read a Lisp expression from standard input and print the result
133to standard output.
134
135@item @code{nil}
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
139stream}, and must be a non-@code{nil} input stream.
140
141@item @var{symbol}
142A symbol as input stream is equivalent to the symbol's function
143definition (if any).
144@end table
145
146 Here is an example of reading from a stream that is a buffer, showing
147where point is located before and after:
148
149@example
150@group
151---------- Buffer: foo ----------
152This@point{} is the contents of foo.
153---------- Buffer: foo ----------
154@end group
155
156@group
157(read (get-buffer "foo"))
158 @result{} is
159@end group
160@group
161(read (get-buffer "foo"))
162 @result{} the
163@end group
164
165@group
166---------- Buffer: foo ----------
167This is the@point{} contents of foo.
168---------- Buffer: foo ----------
169@end group
170@end example
171
172@noindent
173Note that the first read skips a space. Reading skips any amount of
174whitespace preceding the significant text.
175
176 Here is an example of reading from a stream that is a marker,
177initially positioned at the beginning of the buffer shown. The value
178read is the symbol @code{This}.
179
180@example
181@group
182
183---------- Buffer: foo ----------
184This is the contents of foo.
185---------- Buffer: foo ----------
186@end group
187
188@group
189(setq m (set-marker (make-marker) 1 (get-buffer "foo")))
190 @result{} #<marker at 1 in foo>
191@end group
192@group
193(read m)
194 @result{} This
195@end group
196@group
197m
198 @result{} #<marker at 5 in foo> ;; @r{Before the first space.}
199@end group
200@end example
201
202 Here we read from the contents of a string:
203
204@example
205@group
206(read "(When in) the course")
207 @result{} (When in)
208@end group
209@end example
210
211 The following example reads from the minibuffer. The
212prompt is: @w{@samp{Lisp expression: }}. (That is always the prompt
213used when you read from the stream @code{t}.) The user's input is shown
214following the prompt.
215
216@example
217@group
218(read t)
219 @result{} 23
220---------- Buffer: Minibuffer ----------
221Lisp expression: @kbd{23 @key{RET}}
222---------- Buffer: Minibuffer ----------
223@end group
224@end example
225
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
228variable @code{useless-list} to a list of characters. Then each call to
229the function @code{useless-stream} obtains the next character in the list
230or unreads a character by adding it to the front of the list.
231
232@example
233@group
234(setq useless-list (append "XY()" nil))
235 @result{} (88 89 40 41)
236@end group
237
238@group
239(defun useless-stream (&optional unread)
240 (if 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
245@end group
246@end example
247
248@noindent
249Now we read using the stream thus constructed:
250
251@example
252@group
253(read 'useless-stream)
254 @result{} XY
255@end group
256
257@group
258useless-list
259 @result{} (40 41)
260@end group
261@end example
262
263@noindent
264Note that the open and close parentheses remain in the list. The Lisp
265reader encountered the open parenthesis, decided that it ended the
266input, and unread it. Another attempt to read from the stream at this
267point would read @samp{()} and return @code{nil}.
268
b8d4c8d0
GM
269@node Input Functions
270@section Input Functions
271
272 This section describes the Lisp functions and variables that pertain
273to reading.
274
275 In the functions below, @var{stream} stands for an input stream (see
276the previous section). If @var{stream} is @code{nil} or omitted, it
277defaults to the value of @code{standard-input}.
278
279@kindex end-of-file
280 An @code{end-of-file} error is signaled if reading encounters an
281unterminated list, vector, or string.
282
283@defun read &optional stream
284This function reads one textual Lisp expression from @var{stream},
285returning it as a Lisp object. This is the basic Lisp input function.
286@end defun
287
288@defun read-from-string string &optional start end
289@cindex string to object
290This 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,
292and whose @sc{cdr} is an integer giving the position of the next
293remaining character in the string (i.e., the first one not read).
294
295If @var{start} is supplied, then reading begins at index @var{start} in
296the 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
298the rest of the string were not there.
299
300For example:
301
302@example
303@group
304(read-from-string "(setq x 55) (setq y 5)")
305 @result{} ((setq x 55) . 11)
306@end group
307@group
308(read-from-string "\"A short string\"")
309 @result{} ("A short string" . 16)
310@end group
311
312@group
313;; @r{Read starting at the first character.}
314(read-from-string "(list 112)" 0)
315 @result{} ((list 112) . 10)
316@end group
317@group
318;; @r{Read starting at the second character.}
319(read-from-string "(list 112)" 1)
320 @result{} (list . 5)
321@end group
322@group
323;; @r{Read starting at the seventh character,}
324;; @r{and stopping at the ninth.}
325(read-from-string "(list 112)" 6 8)
326 @result{} (11 . 8)
327@end group
328@end example
329@end defun
330
331@defvar standard-input
332This variable holds the default input stream---the stream that
333@code{read} uses when the @var{stream} argument is @code{nil}.
334The default is @code{t}, meaning use the minibuffer.
335@end defvar
336
dd449674
CY
337@defvar read-circle
338If non-@code{nil}, this variable enables the reading of circular and
339shared structures. @xref{Circular Objects}. Its default value is
340@code{t}.
341@end defvar
342
b8d4c8d0
GM
343@node Output Streams
344@section Output Streams
345@cindex stream (for printing)
346@cindex output stream
347
348 An output stream specifies what to do with the characters produced
349by printing. Most print functions accept an output stream as an
350optional argument. Here are the possible types of output stream:
351
352@table @asis
353@item @var{buffer}
354@cindex buffer output stream
355The output characters are inserted into @var{buffer} at point.
356Point advances as characters are inserted.
357
358@item @var{marker}
359@cindex marker output stream
360The output characters are inserted into the buffer that @var{marker}
361points into, at the marker position. The marker position advances as
362characters are inserted. The value of point in the buffer has no effect
363on printing when the stream is a marker, and this kind of printing
364does not move point (except that if the marker points at or before the
365position of point, point advances with the surrounding text, as
366usual).
367
368@item @var{function}
369@cindex function output stream
370The output characters are passed to @var{function}, which is responsible
371for storing them away. It is called with a single character as
372argument, as many times as there are characters to be output, and
373is responsible for storing the characters wherever you want to put them.
374
375@item @code{t}
376@cindex @code{t} output stream
377The output characters are displayed in the echo area.
378
379@item @code{nil}
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
383stream}, and must not be @code{nil}.
384
385@item @var{symbol}
386A symbol as output stream is equivalent to the symbol's function
387definition (if any).
388@end table
389
390 Many of the valid output streams are also valid as input streams. The
391difference between input and output streams is therefore more a matter
392of how you use a Lisp object, than of different types of object.
393
394 Here is an example of a buffer used as an output stream. Point is
395initially located as shown immediately before the @samp{h} in
396@samp{the}. At the end, point is located directly before that same
397@samp{h}.
398
399@cindex print example
400@example
401@group
402---------- Buffer: foo ----------
403This is t@point{}he contents of foo.
404---------- Buffer: foo ----------
405@end group
406
407(print "This is the output" (get-buffer "foo"))
408 @result{} "This is the output"
409
410@group
411---------- Buffer: foo ----------
412This is t
413"This is the output"
414@point{}he contents of foo.
415---------- Buffer: foo ----------
416@end group
417@end example
418
419 Now we show a use of a marker as an output stream. Initially, the
420marker is in buffer @code{foo}, between the @samp{t} and the @samp{h} in
421the word @samp{the}. At the end, the marker has advanced over the
422inserted text so that it remains positioned before the same @samp{h}.
423Note that the location of point, shown in the usual fashion, has no
424effect.
425
426@example
427@group
428---------- Buffer: foo ----------
429This is the @point{}output
430---------- Buffer: foo ----------
431@end group
432
433@group
434(setq m (copy-marker 10))
435 @result{} #<marker at 10 in foo>
436@end group
437
438@group
439(print "More output for foo." m)
440 @result{} "More output for foo."
441@end group
442
443@group
444---------- Buffer: foo ----------
445This is t
446"More output for foo."
447he @point{}output
448---------- Buffer: foo ----------
449@end group
450
451@group
452m
453 @result{} #<marker at 34 in foo>
454@end group
455@end example
456
457 The following example shows output to the echo area:
458
459@example
460@group
461(print "Echo Area output" t)
462 @result{} "Echo Area output"
463---------- Echo Area ----------
464"Echo Area output"
465---------- Echo Area ----------
466@end group
467@end example
468
469 Finally, we show the use of a function as an output stream. The
470function @code{eat-output} takes each character that it is given and
471conses it onto the front of the list @code{last-output} (@pxref{Building
472Lists}). At the end, the list contains all the characters output, but
473in reverse order.
474
475@example
476@group
477(setq last-output nil)
478 @result{} nil
479@end group
480
481@group
482(defun eat-output (c)
483 (setq last-output (cons c last-output)))
484 @result{} eat-output
485@end group
486
487@group
488(print "This is the output" 'eat-output)
489 @result{} "This is the output"
490@end group
491
492@group
493last-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)
496@end group
497@end example
498
499@noindent
500Now we can put the output in the proper order by reversing the list:
501
502@example
503@group
504(concat (nreverse last-output))
505 @result{} "
506\"This is the output\"
507"
508@end group
509@end example
510
511@noindent
512Calling @code{concat} converts the list to a string so you can see its
513contents more clearly.
514
515@node Output Functions
516@section Output Functions
517
518 This section describes the Lisp functions for printing Lisp
519objects---converting objects into their printed representation.
520
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
526output when necessary so that it can be read properly. The quoting
527characters used are @samp{"} and @samp{\}; they distinguish strings from
528symbols, and prevent punctuation characters in strings and symbols from
529being taken as delimiters when reading. @xref{Printed Representation},
530for full details. You specify quoting or no quoting by the choice of
531printing function.
532
533 If the text is to be read back into Lisp, then you should print with
534quoting characters to avoid ambiguity. Likewise, if the purpose is to
535describe a Lisp object clearly for a Lisp programmer. However, if the
536purpose of the output is to look nice for humans, then it is usually
537better to print without quoting.
538
539 Lisp objects can refer to themselves. Printing a self-referential
540object in the normal way would require an infinite amount of text, and
541the attempt could cause infinite recursion. Emacs detects such
542recursion and prints @samp{#@var{level}} instead of recursively printing
543an object already being printed. For example, here @samp{#0} indicates
544a recursive reference to the object at level 0 of the current print
545operation:
546
547@example
548(setq foo (list nil))
549 @result{} (nil)
550(setcar foo foo)
551 @result{} (#0)
552@end example
553
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}.
558
559@defun print object &optional stream
560@cindex Lisp printer
561The @code{print} function is a convenient way of printing. It outputs
562the printed representation of @var{object} to @var{stream}, printing in
563addition one newline before @var{object} and another after it. Quoting
564characters are used. @code{print} returns @var{object}. For example:
565
566@example
567@group
568(progn (print 'The\ cat\ in)
569 (print "the hat")
570 (print " came back"))
571 @print{}
572 @print{} The\ cat\ in
573 @print{}
574 @print{} "the hat"
575 @print{}
576 @print{} " came back"
577 @result{} " came back"
578@end group
579@end example
580@end defun
581
582@defun prin1 object &optional stream
583This 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}.
587
588@example
589@group
590(progn (prin1 'The\ cat\ in)
591 (prin1 "the hat")
592 (prin1 " came back"))
593 @print{} The\ cat\ in"the hat"" came back"
594 @result{} " came back"
595@end group
596@end example
597@end defun
598
599@defun princ object &optional stream
600This function outputs the printed representation of @var{object} to
601@var{stream}. It returns @var{object}.
602
603This function is intended to produce output that is readable by people,
604not by @code{read}, so it doesn't insert quoting characters and doesn't
605put double-quotes around the contents of strings. It does not add any
606spacing between calls.
607
608@example
609@group
610(progn
611 (princ 'The\ cat)
612 (princ " in the \"hat\""))
613 @print{} The cat in the "hat"
614 @result{} " in the \"hat\""
615@end group
616@end example
617@end defun
618
619@defun terpri &optional stream
620@cindex newline in print
621This function outputs a newline to @var{stream}. The name stands
16152b76 622for ``terminate print''.
b8d4c8d0
GM
623@end defun
624
625@defun write-char character &optional stream
626This function outputs @var{character} to @var{stream}. It returns
627@var{character}.
628@end defun
629
630@defun prin1-to-string object &optional noescape
631@cindex object to string
632This function returns a string containing the text that @code{prin1}
633would have printed for the same argument.
634
635@example
636@group
637(prin1-to-string 'foo)
638 @result{} "foo"
639@end group
640@group
641(prin1-to-string (mark-marker))
642 @result{} "#<marker at 2773 in strings.texi>"
643@end group
644@end example
645
646If @var{noescape} is non-@code{nil}, that inhibits use of quoting
647characters in the output. (This argument is supported in Emacs versions
64819 and later.)
649
650@example
651@group
652(prin1-to-string "foo")
653 @result{} "\"foo\""
654@end group
655@group
656(prin1-to-string "foo" t)
657 @result{} "foo"
658@end group
659@end example
660
661See @code{format}, in @ref{Formatting Strings}, for other ways to obtain
662the printed representation of a Lisp object as a string.
663@end defun
664
665@defmac with-output-to-string body@dots{}
666This macro executes the @var{body} forms with @code{standard-output} set
667up to feed output into a string. Then it returns that string.
668
669For example, if the current buffer name is @samp{foo},
670
671@example
672(with-output-to-string
673 (princ "The buffer is ")
674 (princ (buffer-name)))
675@end example
676
677@noindent
678returns @code{"The buffer is foo"}.
679@end defmac
680
36cb87a1
LMI
681@defun pp object &optional stream
682This function outputs @var{object} to @var{stream}, just like
683@code{prin1}, but does it in a more ``pretty'' way. That is, it'll
684indent and fill the object to make it more readable for humans.
685@end defun
686
b8d4c8d0
GM
687@node Output Variables
688@section Variables Affecting Output
689@cindex output-controlling variables
690
691@defvar standard-output
692The value of this variable is the default output stream---the stream
693that print functions use when the @var{stream} argument is @code{nil}.
694The default is @code{t}, meaning display in the echo area.
695@end defvar
696
697@defvar print-quoted
698If this is non-@code{nil}, that means to print quoted forms using
34106abe
CY
699abbreviated reader syntax, e.g.@: @code{(quote foo)} prints as
700@code{'foo}, and @code{(function foo)} as @code{#'foo}.
b8d4c8d0
GM
701@end defvar
702
703@defvar print-escape-newlines
704@cindex @samp{\n} in print
705@cindex escape characters
706If this variable is non-@code{nil}, then newline characters in strings
707are printed as @samp{\n} and formfeeds are printed as @samp{\f}.
708Normally these characters are printed as actual newlines and formfeeds.
709
710This variable affects the print functions @code{prin1} and @code{print}
711that print with quoting. It does not affect @code{princ}. Here is an
712example using @code{prin1}:
713
714@example
715@group
716(prin1 "a\nb")
717 @print{} "a
718 @print{} b"
719 @result{} "a
720b"
721@end group
722
723@group
724(let ((print-escape-newlines t))
725 (prin1 "a\nb"))
726 @print{} "a\nb"
727 @result{} "a
728b"
729@end group
730@end example
731
732@noindent
733In 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.
736@end defvar
737
738@defvar print-escape-nonascii
739If this variable is non-@code{nil}, then unibyte non-@acronym{ASCII}
740characters in strings are unconditionally printed as backslash sequences
741by the print functions @code{prin1} and @code{print} that print with
742quoting.
743
744Those functions also use backslash sequences for unibyte non-@acronym{ASCII}
745characters, regardless of the value of this variable, when the output
746stream is a multibyte buffer or a marker pointing into one.
747@end defvar
748
749@defvar print-escape-multibyte
750If this variable is non-@code{nil}, then multibyte non-@acronym{ASCII}
751characters in strings are unconditionally printed as backslash sequences
752by the print functions @code{prin1} and @code{print} that print with
753quoting.
754
755Those functions also use backslash sequences for multibyte
756non-@acronym{ASCII} characters, regardless of the value of this variable,
757when the output stream is a unibyte buffer or a marker pointing into
758one.
759@end defvar
760
761@defvar print-length
762@cindex printing limits
763The value of this variable is the maximum number of elements to print in
764any list, vector or bool-vector. If an object being printed has more
765than this many elements, it is abbreviated with an ellipsis.
766
767If the value is @code{nil} (the default), then there is no limit.
768
769@example
770@group
771(setq print-length 2)
772 @result{} 2
773@end group
774@group
775(print '(1 2 3 4 5))
776 @print{} (1 2 ...)
777 @result{} (1 2 ...)
778@end group
779@end example
780@end defvar
781
782@defvar print-level
783The value of this variable is the maximum depth of nesting of
784parentheses and brackets when printed. Any list or vector at a depth
785exceeding this limit is abbreviated with an ellipsis. A value of
786@code{nil} (which is the default) means no limit.
787@end defvar
788
789@defopt eval-expression-print-length
790@defoptx eval-expression-print-level
791These are the values for @code{print-length} and @code{print-level}
792used by @code{eval-expression}, and thus, indirectly, by many
793interactive evaluation commands (@pxref{Lisp Eval,, Evaluating
794Emacs-Lisp Expressions, emacs, The GNU Emacs Manual}).
795@end defopt
796
797 These variables are used for detecting and reporting circular
798and shared structure:
799
800@defvar print-circle
dd449674 801If non-@code{nil}, this variable enables detection of circular and
544c5fc9 802shared structure in printing. @xref{Circular Objects}.
b8d4c8d0
GM
803@end defvar
804
805@defvar print-gensym
806If non-@code{nil}, this variable enables detection of uninterned symbols
807(@pxref{Creating Symbols}) in printing. When this is enabled,
808uninterned symbols print with the prefix @samp{#:}, which tells the Lisp
809reader to produce an uninterned symbol.
810@end defvar
811
812@defvar print-continuous-numbering
813If non-@code{nil}, that means number continuously across print calls.
814This affects the numbers printed for @samp{#@var{n}=} labels and
815@samp{#@var{m}#} references.
816
817Don't set this variable with @code{setq}; you should only bind it
818temporarily to @code{t} with @code{let}. When you do that, you should
819also bind @code{print-number-table} to @code{nil}.
820@end defvar
821
822@defvar print-number-table
823This variable holds a vector used internally by printing to implement
824the @code{print-circle} feature. You should not use it except
825to bind it to @code{nil} when you bind @code{print-continuous-numbering}.
826@end defvar
827
828@defvar float-output-format
829This variable specifies how to print floating point numbers. Its
830default value is @code{nil}, meaning use the shortest output
831that represents the number without losing information.
832
833To control output format more precisely, you can put a string in this
834variable. The string should hold a @samp{%}-specification to be used
835in the C function @code{sprintf}. For further restrictions on what
836you can use, see the variable's documentation string.
837@end defvar