From: Jim Porter <jporterbugs@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>, Eli Zaretskii <eliz@gnu.org>
Cc: 61024@debbugs.gnu.org
Subject: bug#61024: 29.0.60; [PATCH] Eshell errors out when trying to redirect output of a remote process
Date: Mon, 23 Jan 2023 09:47:03 -0800 [thread overview]
Message-ID: <40898fb1-9a3b-9cf5-6c62-acc16ccc76e5@gmail.com> (raw)
In-Reply-To: <877cxdi72h.fsf@gmx.de>
On 1/23/2023 7:50 AM, Michael Albinus wrote:
> Pipe processes are always tricky for Tramp. I *believe* redirecting
> stdout and stderr to different buffers shall work, see "test6" of
> tramp-test30-make-process. But I remember also that this was painful to
> implement and test.
Yeah, I took a look at the Tramp code and it's pretty tricky. I'll see
if I can come up with something for Emacs 30 though (maybe we could
update the 'make-process' API to make this easier for Tramp?).
I'll merge this simple fix to Emacs 29 shortly then.
>>> I'm actually surprised no one has filed a bug on this already.
>>
>> Maybe it tells us how many people use this combination?
>
> So do we want to reopen this can of worms, and see what happens with
> Tramp? But perhaps it is a problem in Eshell, which tries to create its
> own pipe process?
I'd certainly expect to see bug reports if this had shipped as part of a
final Emacs release, but I think it does say that not many people use
Tramp + Eshell on development builds. (Which, if anything, is mostly a
sign to me that I need to be extra-careful when testing combinations of
features like this, since people might not report bugs until after the
release.)
next prev parent reply other threads:[~2023-01-23 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 7:07 bug#61024: 29.0.60; [PATCH] Eshell errors out when trying to redirect output of a remote process Jim Porter
2023-01-23 13:21 ` Eli Zaretskii
2023-01-23 15:50 ` Michael Albinus
2023-01-23 17:47 ` Jim Porter [this message]
2023-01-23 17:51 ` Jim Porter
2023-01-23 18:25 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40898fb1-9a3b-9cf5-6c62-acc16ccc76e5@gmail.com \
--to=jporterbugs@gmail.com \
--cc=61024@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.