From c1aa486418412c6e6eff46ceb7ff8b9276fa5263 Mon Sep 17 00:00:00 2001 From: Jesper Harder Date: Sun, 21 Nov 2004 19:39:59 +0000 Subject: [PATCH] (Synchronous Processes, Output from Processes): Markup fix. --- lispref/ChangeLog | 5 +++++ lispref/processes.texi | 6 +++--- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/lispref/ChangeLog b/lispref/ChangeLog index 5e5cdfc8955..5bfe3793e73 100644 --- a/lispref/ChangeLog +++ b/lispref/ChangeLog @@ -1,3 +1,8 @@ +2004-11-21 Jesper Harder + + * processes.texi (Synchronous Processes, Output from Processes): + Markup fix. + 2004-11-20 Richard M. Stallman * positions.texi (Skipping Characters): skip-chars-forward diff --git a/lispref/processes.texi b/lispref/processes.texi index 35041677b80..6b772819b81 100644 --- a/lispref/processes.texi +++ b/lispref/processes.texi @@ -328,7 +328,7 @@ The arguments are handled in almost the same way as for Some file handlers may not support all combinations and forms of the arguments @var{infile}, @var{buffer}, and @var{display}. For example, -some file handlers might behave as if @var{display} was nil, +some file handlers might behave as if @var{display} was @code{nil}, regardless of the value actually passed. As another example, some file handlers might not support separating standard output and error output by way of the @var{buffer} argument. @@ -975,7 +975,7 @@ On some systems, when Emacs reads the output from a subprocess, the output data is read in very small blocks, potentially resulting in very poor performance. This behaviour can be remedied to some extent by setting the variable @var{process-adaptive-read-buffering} to a -non-nil value (the default), as it will automatically delay reading +non-@code{nil} value (the default), as it will automatically delay reading from such processes, thus allowing them to produce more output before Emacs tries to read it. @end defvar @@ -1316,7 +1316,7 @@ nonzero @var{millisec}. @c Emacs 21.4 feature If @var{process} is a process, and the argument @var{just-this-one} is -non-nil, only output from that process is handled, suspending output +non-@code{nil}, only output from that process is handled, suspending output from other processes until some output has been received from that process or the timeout expires. If @var{just-this-one} is an integer, also inhibit running timers. This feature is generally not -- 2.39.2