Commit e8c07cae authored by Michael Albinus's avatar Michael Albinus

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
parent d9d592dd
Pipeline #1423 passed with stage
in 58 minutes and 28 seconds
......@@ -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
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment