# HG changeset patch
# User Chong Yidong <cyd@stupidchicken.com>
# Date 1236647139 0
# Node ID 245a1f77b8403716d734501e80b245aef8ca70da
# Parent  c03f234287b6029d66a85fa03451711587c44369
(Feval_buffer): Doc fix.

diff -r c03f234287b6 -r 245a1f77b840 src/lread.c
--- a/src/lread.c	Tue Mar 10 01:05:31 2009 +0000
+++ b/src/lread.c	Tue Mar 10 01:05:39 2009 +0000
@@ -1803,18 +1803,16 @@
 
 DEFUN ("eval-buffer", Feval_buffer, Seval_buffer, 0, 5, "",
        doc: /* Execute the current buffer as Lisp code.
-Programs can pass two arguments, BUFFER and PRINTFLAG.
+When called from a Lisp program (i.e., not interactively), this
+function accepts up to five optional arguments:
 BUFFER is the buffer to evaluate (nil means use current buffer).
 PRINTFLAG controls printing of output:
-A value of nil means discard it; anything else is stream for print.
-
-If the optional third argument FILENAME is non-nil,
-it specifies the file name to use for `load-history'.
-The optional fourth argument UNIBYTE specifies `load-convert-to-unibyte'
-for this invocation.
-
-The optional fifth argument DO-ALLOW-PRINT, if non-nil, specifies that
-`print' and related functions should work normally even if PRINTFLAG is nil.
+ A value of nil means discard it; anything else is stream for print.
+FILENAME specifies the file name to use for `load-history'.
+UNIBYTE, if non-nil, specifies `load-convert-to-unibyte' for this
+ invocation.
+DO-ALLOW-PRINT, if non-nil, specifies that `print' and related
+ functions should work normally even if PRINTFLAG is nil.
 
 This function preserves the position of point.  */)
      (buffer, printflag, filename, unibyte, do_allow_print)