Mercurial > emacs
comparison lispref/os.texi @ 36873:705d5129bb72
batch read from minibuffer
author | Dave Love <fx@gnu.org> |
---|---|
date | Mon, 19 Mar 2001 14:54:02 +0000 |
parents | 26912db550c3 |
children | 557aaff6fb23 |
comparison
equal
deleted
inserted
replaced
36872:da90c393ed4e | 36873:705d5129bb72 |
---|---|
1915 calls @var{function} with no arguments. | 1915 calls @var{function} with no arguments. |
1916 | 1916 |
1917 Any Lisp program output that would normally go to the echo area, | 1917 Any Lisp program output that would normally go to the echo area, |
1918 either using @code{message}, or using @code{prin1}, etc., with @code{t} | 1918 either using @code{message}, or using @code{prin1}, etc., with @code{t} |
1919 as the stream, goes instead to Emacs's standard error descriptor when | 1919 as the stream, goes instead to Emacs's standard error descriptor when |
1920 in batch mode. Thus, Emacs behaves much like a noninteractive | 1920 in batch mode. Similarly, input that would normally come from the |
1921 minibuffer is read from the standard input descriptor. | |
1922 Thus, Emacs behaves much like a noninteractive | |
1921 application program. (The echo area output that Emacs itself normally | 1923 application program. (The echo area output that Emacs itself normally |
1922 generates, such as command echoing, is suppressed entirely.) | 1924 generates, such as command echoing, is suppressed entirely.) |
1923 | 1925 |
1924 @defvar noninteractive | 1926 @defvar noninteractive |
1925 This variable is non-@code{nil} when Emacs is running in batch mode. | 1927 This variable is non-@code{nil} when Emacs is running in batch mode. |