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