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 #35 received at 72117 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Jim Porter <jporterbugs <at> gmail.com>
Cc: the_wurfkreuz <at> proton.me, 72117 <at> debbugs.gnu.org
Subject: Re: bug#72117: Command doesn't execute correctly in eshell
Date: Sat, 27 Jul 2024 09:40:10 +0300
> Date: Fri, 26 Jul 2024 22:18:22 -0700
> From: Jim Porter <jporterbugs <at> gmail.com>
> Cc: eliz <at> gnu.org
> 
> On 7/14/2024 6:01 PM, Jim Porter wrote:
> > On 7/14/2024 12:33 PM, the_wurfkreuz via Bug reports for GNU Emacs, the 
> > Swiss army knife of text editors wrote:
> >   But that's not the most interesting part. I can execute the
> >> command with 'eshell/sudo'. But after the command execution emacs will
> >> take the whole CPU processing time if i have 
> >> '(global-display-line-numbers-mode 1)'
> >> option enabled.
> > 
> > I can't reproduce this particular issue, but I can reproduce *an* issue. 
> > It seems to be due to "head -10" exiting early (as it should), which 
> > results in a broken pipe. However, Eshell's broken pipe handling wasn't 
> > properly cleaning up the process ("grep" in this example).
> 
> Eli, would this patch (re-attached here) be ok for Emacs 30? It's not a 
> perfect solution (the fix currently on master is much better), but it's 
> the least-risky change to this code that I could make, and it should 
> improve matters somewhat for the release branch.

This is okay for emacs-30, thanks.




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.