all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: the_wurfkreuz@proton.me, 72117@debbugs.gnu.org
Subject: bug#72117: Command doesn't execute correctly in eshell
Date: Sat, 27 Jul 2024 09:40:10 +0300	[thread overview]
Message-ID: <868qxn2v91.fsf@gnu.org> (raw)
In-Reply-To: <51486b9f-cc61-62af-8529-8850fb98f051@gmail.com> (message from Jim Porter on Fri, 26 Jul 2024 22:18:22 -0700)

> Date: Fri, 26 Jul 2024 22:18:22 -0700
> From: Jim Porter <jporterbugs@gmail.com>
> Cc: eliz@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.





  reply	other threads:[~2024-07-27  6:40 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=868qxn2v91.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=72117@debbugs.gnu.org \
    --cc=jporterbugs@gmail.com \
    --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 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.