summaryrefslogtreecommitdiff
path: root/lispref
diff options
context:
space:
mode:
authorDave Love <fx@gnu.org>2001-03-19 14:54:02 +0000
committerDave Love <fx@gnu.org>2001-03-19 14:54:02 +0000
commitd70ba855bde44101cecd2a47027bc036ad2728c4 (patch)
treec7312266ed14d11fd5ad5c78a051d1a5a622b27b /lispref
parent61b23410328cce5b22b15d06b939dead453e2721 (diff)
downloademacs-d70ba855bde44101cecd2a47027bc036ad2728c4.tar.gz
batch read from minibuffer
Diffstat (limited to 'lispref')
-rw-r--r--lispref/os.texi4
1 files changed, 3 insertions, 1 deletions
diff --git a/lispref/os.texi b/lispref/os.texi
index 2bc4ccb6f57..bd05d39cf44 100644
--- a/lispref/os.texi
+++ b/lispref/os.texi
@@ -1917,7 +1917,9 @@ calls @var{function} with no arguments.
Any Lisp program output that would normally go to the echo area,
either using @code{message}, or using @code{prin1}, etc., with @code{t}
as the stream, goes instead to Emacs's standard error descriptor when
-in batch mode. Thus, Emacs behaves much like a noninteractive
+in batch mode. Similarly, input that would normally come from the
+minibuffer is read from the standard input descriptor.
+Thus, Emacs behaves much like a noninteractive
application program. (The echo area output that Emacs itself normally
generates, such as command echoing, is suppressed entirely.)