aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard M. Stallman2004-11-25 03:15:19 +0000
committerRichard M. Stallman2004-11-25 03:15:19 +0000
commitf8684c07a40950d743892d992d2f175f70b7d23e (patch)
treeb15f6f5bb5ee63c414c277f08effaf95018b214c
parent5e859db984c1c4fe07efbd7d77a3588c86533829 (diff)
downloademacs-f8684c07a40950d743892d992d2f175f70b7d23e.tar.gz
emacs-f8684c07a40950d743892d992d2f175f70b7d23e.zip
(Synchronous Processes): Grammar fix.
-rw-r--r--lispref/processes.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/lispref/processes.texi b/lispref/processes.texi
index 6b772819b81..51d3d4c9845 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 @code{nil}, 331some file handlers might behave as if @var{display} were @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.