From e8c07cae5faca34c64568a393cdc2da59a295c86 Mon Sep 17 00:00:00 2001 From: Michael Albinus Date: Tue, 23 Apr 2019 16:07:38 +0200 Subject: [PATCH] Remote processes cannot use a pipe process for stderr * doc/lispref/processes.texi (Asynchronous Processes): (Accepting Output): Remote processes cannot use a pipe process for stderr. --- doc/lispref/processes.texi | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/doc/lispref/processes.texi b/doc/lispref/processes.texi index c08b14c72c5..69f781e3a9f 100644 --- a/doc/lispref/processes.texi +++ b/doc/lispref/processes.texi @@ -734,7 +734,11 @@ current working directory is the local name component of Depending on the implementation of the file name handler, it might not be possible to apply @var{filter} or @var{sentinel} to the resulting -process object. @xref{Filter Functions}, and @ref{Sentinels}. +process object. The @code{:stderr} argument cannot be a pipe process, +file name handlers do not support pipe processes for this. A buffer +as @code{:stderr} argument is accepted, its contents is shown without +the use of pipe processes. @xref{Filter Functions}, @ref{Sentinels}, +and @ref{Accepting Output}. Some file name handlers may not support @code{make-process}. In such cases, this function does nothing and returns @code{nil}. @@ -1908,6 +1912,9 @@ code: (while (accept-process-output stderr-process)) @end example +Reading pending standard error from a process running on a remote host +is not possible this way. + @node Processes and Threads @subsection Processes and Threads @cindex processes, threads -- 2.39.2