Commit 4f5d565f authored by Glenn Morris's avatar Glenn Morris
Browse files

* processes.texi (Accepting Output): Discourage use of `millisec' argument.

parent 62f4b18c
......@@ -3,6 +3,7 @@
* processes.texi (Process Information, Input to Processes)
(Signals to Processes, Output from Processes, Process Buffers)
(Filter Functions, Decoding Output): Copyedits.
(Accepting Output): Discourage use of `millisec' argument.
2012-04-15 Glenn Morris <rgm@gnu.org>
......
......@@ -1465,7 +1465,6 @@ output is inserted in the associated buffers or given to their filter
functions. If @var{process} is non-@code{nil} then this function does
not return until some output has been received from @var{process}.
@c Emacs 19 feature
The arguments @var{seconds} and @var{millisec} let you specify timeout
periods. The former specifies a period measured in seconds and the
latter specifies one measured in milliseconds. The two time periods
......@@ -1473,10 +1472,10 @@ thus specified are added together, and @code{accept-process-output}
returns after that much time, whether or not there has been any
subprocess output.
The argument @var{millisec} is semi-obsolete nowadays because
@var{seconds} can be a floating point number to specify waiting a
fractional number of seconds. If @var{seconds} is 0, the function
accepts whatever output is pending but does not wait.
The argument @var{millisec} is obsolete (and should not be used),
because @var{seconds} can be a floating point number to specify
waiting a fractional number of seconds. If @var{seconds} is 0, the
function accepts whatever output is pending but does not wait.
@c Emacs 22.1 feature
If @var{process} is a process, and the argument @var{just-this-one} is
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment