From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: phst@google.com, emacs-devel@gnu.org
Subject: Re: master 3b4e312: Improve documentation around standard error pipes (Bug#35328).
Date: Tue, 23 Apr 2019 09:11:23 +0200 [thread overview]
Message-ID: <877ebl9ox0.fsf@gmx.de> (raw)
In-Reply-To: <83d0ld5l7d.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 23 Apr 2019 08:45:10 +0300")
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
Eli Zaretskii <eliz@gnu.org> 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?
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1399 bytes --]
*** /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
next prev parent reply other threads:[~2019-04-23 7:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190422140753.20611.97812@vcs0.savannah.gnu.org>
[not found] ` <20190422140756.5C1042088F@vcs0.savannah.gnu.org>
2019-04-22 20:59 ` master 3b4e312: Improve documentation around standard error pipes (Bug#35328) Michael Albinus
2019-04-23 5:45 ` Eli Zaretskii
2019-04-23 7:11 ` Michael Albinus [this message]
2019-04-23 10:28 ` Eli Zaretskii
2019-04-23 12:05 ` Michael Albinus
2019-04-23 12:16 ` Eli Zaretskii
2019-04-23 14:09 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ebl9ox0.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=phst@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).