procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Remote processes cannot use a pipe process for stderr

Browse source 
* doc/lispref/processes.texi (Asynchronous Processes):
(Accepting Output): Remote processes cannot use a pipe process for
stderr.
This commit is contained in:
Michael Albinus 2019-04-23 16:07:38 +02:00
parent d9d592dd44
commit e8c07cae5f
1 changed files with 8 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/lispref/processes.texi
View file

@ -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