GNU bug report logs - #72117
Command doesn't execute correctly in eshell

Previous Next

Package: emacs;

Reported by: the_wurfkreuz <the_wurfkreuz <at> proton.me>

Date: Sun, 14 Jul 2024 19:34:01 UTC

Severity: normal

Done: Jim Porter <jporterbugs <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #23 received at 72117 <at> debbugs.gnu.org (full text, mbox):

From: Jim Porter <jporterbugs <at> gmail.com>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: the_wurfkreuz <the_wurfkreuz <at> proton.me>, 72117 <at> debbugs.gnu.org
Subject: Re: bug#72117: Command doesn't execute correctly in eshell
Date: Thu, 18 Jul 2024 08:38:53 -0700
On 7/18/2024 2:31 AM, Michael Albinus via Bug reports for GNU Emacs, the 
Swiss army knife of text editors wrote:
> Jim Porter <jporterbugs <at> gmail.com> writes:
> 
>> 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?

Isn't a process object with the 'remote-pid' property set sufficient 
here? From my understanding of the code, REMOTE is redundant in that case.

(I'll probably need the REMOTE argument in some other Eshell code that 
we've been discussing recently, but not here I think...)




This bug report was last modified 356 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.