From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61024@debbugs.gnu.org, Jim Porter <jporterbugs@gmail.com>
Subject: bug#61024: 29.0.60; [PATCH] Eshell errors out when trying to redirect output of a remote process
Date: Mon, 23 Jan 2023 16:50:14 +0100 [thread overview]
Message-ID: <877cxdi72h.fsf@gmx.de> (raw)
In-Reply-To: <83wn5didxu.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 23 Jan 2023 15:21:49 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
Hi,
>> ~ $ cd /sudo::
>> /sudo:root@host:~ # *echo hi there > #<foo>
>> Wrong type argument: "bufferp echo-stderr"
>>
>> (Any other Tramp method should reproduce this issue.) That's because the
>> echo command is being redirected to two places: stdout is going to the
>> buffer "foo", and stderr is going to the Eshell buffer (via a pipe
>> process). However, that doesn't work for Tramp processes.
>>
>> Attached is a fix with a test. I think this should definitely go in
>> Emacs 29, since it's a pretty bad regression.
>
> Fine by me, unless Michael objects or has better ideas.
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.
>> 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?
Best regards, Michael.
next prev parent reply other threads:[~2023-01-23 15:50 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 [this message]
2023-01-23 17:47 ` Jim Porter
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=877cxdi72h.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=61024@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jporterbugs@gmail.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 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.