From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
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 15:21:49 +0200 [thread overview]
Message-ID: <83wn5didxu.fsf@gnu.org> (raw)
In-Reply-To: <230f0e06-f47a-6a0d-93de-222ca16f7213@gmail.com> (message from Jim Porter on Sun, 22 Jan 2023 23:07:58 -0800)
> Date: Sun, 22 Jan 2023 23:07:58 -0800
> From: Jim Porter <jporterbugs@gmail.com>
>
> ~ $ 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.
> I'm actually surprised no one has filed a bug on this already.
Maybe it tells us how many people use this combination?
next prev parent reply other threads:[~2023-01-23 13:21 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 [this message]
2023-01-23 15:50 ` Michael Albinus
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
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=83wn5didxu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61024@debbugs.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 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).