Fix recent change in lispref/processes.texi.

* doc/lispref/processes.texi (Asynchronous Processes): Clarify
wording.  Suggested by Thomas Fitzsimmons <fitzsim@fitzsim.org>.
(Bug#33050)
This commit is contained in:
Eli Zaretskii 2018-10-27 21:47:59 +03:00
parent df64da8eb8
commit d192c1671c

View file

@ -601,13 +601,13 @@ Shell mode, because they allow for job control (@kbd{C-c}, @kbd{C-z},
etc.)@: between the process and its children, and because interactive etc.)@: between the process and its children, and because interactive
programs treat ptys as terminal devices, whereas pipes don't support programs treat ptys as terminal devices, whereas pipes don't support
these features. However, for subprocesses used by Lisp programs for these features. However, for subprocesses used by Lisp programs for
internal purposes (i.e., with no user interaction), where significant internal purposes (i.e., no user interaction with the subprocess is
amounts of data need to be exchanged between the subprocess and the required), where significant amounts of data need to be exchanged
Lisp program, it is often better to use a pipe, because pipes are between the subprocess and the Lisp program, it is often better to use
more efficient, and because they are immune to stray character a pipe, because pipes are more efficient, and because they are immune
injections that ptys introduce for large (around 500 byte) messages. to stray character injections that ptys introduce for large (around
Also, the total number of ptys is limited on many systems, and it is 500 byte) messages. Also, the total number of ptys is limited on many
good not to waste them unnecessarily. systems, and it is good not to waste them unnecessarily.
@defun make-process &rest args @defun make-process &rest args
This function is the basic low-level primitive for starting This function is the basic low-level primitive for starting