From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
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 08:45:10 +0300 [thread overview]
Message-ID: <83d0ld5l7d.fsf@gnu.org> (raw)
In-Reply-To: <87h8apbvu2.fsf@gmx.de> (message from Michael Albinus on Mon, 22 Apr 2019 22:59:01 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Mon, 22 Apr 2019 22:59:01 +0200
> Cc: Philipp Stephani <phst@google.com>
>
> > +@cindex standard error process
> > +If @var{stderr} is a buffer, Emacs will create a pipe process, the
> > +@dfn{standard error process}. This process will have the default
> > +filter (@pxref{Filter Functions}), sentinel (@pxref{Sentinels}), and
> > +coding systems (@pxref{Default Coding Systems}). On the other hand,
> > +it will use @var{query-flag} as its query-on-exit flag (@pxref{Query
> > +Before Exit}). It will be associated with the @var{stderr} buffer
> > +(@pxref{Process Buffers}) and send its output (which is the standard
> > +error of the main process) there.
>
> FTR, the implementation in Tramp is different from what is described
> here. And honestly, I even don't know, how to implement these two
> processes for the remote case.
>
> The current implementation in Tramp redirects stderr to a temporary
> file, if it is separate from stdout. This temprary file is associated
> with the :stderr buffer, and it runs auto-revert-mode. Maybe not very
> elegant, but working so far.
>
> 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.
next prev parent reply other threads:[~2019-04-23 5:45 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 [this message]
2019-04-23 7:11 ` Michael Albinus
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=83d0ld5l7d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--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).