From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: the_wurfkreuz <the_wurfkreuz@proton.me>, 72117@debbugs.gnu.org
Subject: bug#72117: Command doesn't execute correctly in eshell
Date: Thu, 18 Jul 2024 11:31:09 +0200 [thread overview]
Message-ID: <87frs759nm.fsf@gmx.de> (raw)
In-Reply-To: <835b5821-f522-df6e-286d-5c34962684f7@gmail.com> (Jim Porter's message of "Wed, 17 Jul 2024 22:05:38 -0700")
Jim Porter <jporterbugs@gmail.com> writes:
Hi Jim,
> diff --git a/lisp/eshell/esh-proc.el b/lisp/eshell/esh-proc.el
> index 0dcdf3bb76c..fbeb13362f3 100644
> --- a/lisp/eshell/esh-proc.el
> +++ b/lisp/eshell/esh-proc.el
> + (cond
> + ;; Delay signalling remote processes to prevent
> + ;; "Forbidden reentrant call of Tramp".
> + ((process-get proc 'remote-pid)
> + (run-at-time 0 nil #'signal-process proc 'SIGPIPE))
Shouldn't there be a non-nil REMOTE argument?
Best regards, Michael.
next prev parent reply other threads:[~2024-07-18 9:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 19:33 bug#72117: Command doesn't execute correctly in eshell the_wurfkreuz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-15 1:01 ` Jim Porter
2024-07-16 3:09 ` Jim Porter
[not found] ` <uDv8zx2ccT4dsHYBueowwgc6Hjuz4gs3wLRNNOXllaD4ifNUqW2-7eEYYJDjsG5VzBWGHQGoIJ1aFnbQxMLoacZR71w8v11rIb7GTfhQuus=@proton.me>
2024-07-17 2:09 ` Jim Porter
2024-07-18 5:05 ` Jim Porter
2024-07-18 9:31 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-07-18 15:38 ` Jim Porter
2024-07-18 16:49 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-18 18:26 ` Jim Porter
2024-07-27 5:18 ` Jim Porter
2024-07-27 6:40 ` Eli Zaretskii
2024-07-27 19:14 ` Jim Porter
2024-07-28 7:59 ` Jim Porter
2024-07-28 16:21 ` Jim Porter
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=87frs759nm.fsf@gmx.de \
--to=bug-gnu-emacs@gnu.org \
--cc=72117@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--cc=michael.albinus@gmx.de \
--cc=the_wurfkreuz@proton.me \
/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).