Re: master 3b4e312: Improve documentation around standard error pipes (Bug#35328).

[Michael Albinus]

Eli Zaretskii <address@hidden> writes:

Hi Eli,

>> I don't know whether we shall document this different behavior, or
>> whether we shall find an implementation in Tramp for what is
>> described. For the latter, I would need help, as said. Or at least ideas.
>
> I think we should at least qualify the above description with its
> being accurate for local processes only.

Like this?

*** /tmp/ediffEO055I    2019-04-23 09:08:54.501926412 +0200
--- /home/albinus/src/emacs/doc/lispref/processes.texi  2019-04-23 
09:05:04.977767519 +0200
***************
*** 734,740 ****

  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}.

  Some file name handlers may not support @code{make-process}.  In such
  cases, this function does nothing and returns @code{nil}.
--- 734,743 ----

  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.  The @code{:stderr} argument cannot be a pipe; if it
! is a buffer a different implementation will be used to show the buffer
! contents.  @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,1913 ****
--- 1911,1919 ----
  (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