aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJesper Harder2004-11-21 19:39:59 +0000
committerJesper Harder2004-11-21 19:39:59 +0000
commitc1aa486418412c6e6eff46ceb7ff8b9276fa5263 (patch)
treeaa5c435d75a9f2b4fc61a5f442799e5b93a79804
parentca7cefe702f23b3a6197965479f7b47ec3566c9e (diff)
downloademacs-c1aa486418412c6e6eff46ceb7ff8b9276fa5263.tar.gz
emacs-c1aa486418412c6e6eff46ceb7ff8b9276fa5263.zip
(Synchronous Processes, Output from Processes):
Markup fix.
-rw-r--r--lispref/ChangeLog5
-rw-r--r--lispref/processes.texi6
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 @@
12004-11-21 Jesper Harder <harder@ifa.au.dk>
2
3 * processes.texi (Synchronous Processes, Output from Processes):
4 Markup fix.
5
12004-11-20 Richard M. Stallman <rms@gnu.org> 62004-11-20 Richard M. Stallman <rms@gnu.org>
2 7
3 * positions.texi (Skipping Characters): skip-chars-forward 8 * 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
328 328
329Some file handlers may not support all combinations and forms of the 329Some file handlers may not support all combinations and forms of the
330arguments @var{infile}, @var{buffer}, and @var{display}. For example, 330arguments @var{infile}, @var{buffer}, and @var{display}. For example,
331some file handlers might behave as if @var{display} was nil, 331some file handlers might behave as if @var{display} was @code{nil},
332regardless of the value actually passed. As another example, some 332regardless of the value actually passed. As another example, some
333file handlers might not support separating standard output and error 333file handlers might not support separating standard output and error
334output by way of the @var{buffer} argument. 334output by way of the @var{buffer} argument.
@@ -975,7 +975,7 @@ On some systems, when Emacs reads the output from a subprocess, the
975output data is read in very small blocks, potentially resulting in 975output data is read in very small blocks, potentially resulting in
976very poor performance. This behaviour can be remedied to some extent 976very poor performance. This behaviour can be remedied to some extent
977by setting the variable @var{process-adaptive-read-buffering} to a 977by setting the variable @var{process-adaptive-read-buffering} to a
978non-nil value (the default), as it will automatically delay reading 978non-@code{nil} value (the default), as it will automatically delay reading
979from such processes, thus allowing them to produce more output before 979from such processes, thus allowing them to produce more output before
980Emacs tries to read it. 980Emacs tries to read it.
981@end defvar 981@end defvar
@@ -1316,7 +1316,7 @@ nonzero @var{millisec}.
1316 1316
1317@c Emacs 21.4 feature 1317@c Emacs 21.4 feature
1318If @var{process} is a process, and the argument @var{just-this-one} is 1318If @var{process} is a process, and the argument @var{just-this-one} is
1319non-nil, only output from that process is handled, suspending output 1319non-@code{nil}, only output from that process is handled, suspending output
1320from other processes until some output has been received from that 1320from other processes until some output has been received from that
1321process or the timeout expires. If @var{just-this-one} is an integer, 1321process or the timeout expires. If @var{just-this-one} is an integer,
1322also inhibit running timers. This feature is generally not 1322also inhibit running timers. This feature is generally not