GNU bug report logs - #79079
31.0.50; Piped command output is sometimes lost in Eshell

Previous Next

Full log

View this message in rfc822 format

From: Jim Porter <jporterbugs <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: mail <at> daniel-mendler.de, eggert <at> cs.ucla.edu, 79079 <at> debbugs.gnu.org
Subject: bug#79079: 31.0.50; Piped command output is sometimes lost in Eshell
Date: Fri, 25 Jul 2025 10:16:19 -0700

On 7/24/2025 11:42 PM, Eli Zaretskii wrote:
> Why do we need to emit a message about EPIPE, when we will immediately
> signal an error with the same information?  The message will not be
> seen by users except if they look in *Messages*.

It's just a debug statement for development/testing so that it's clear 
when Emacs runs this block. Since this is a timing-related issue, it's 
hard to guarantee that we hit this condition. While I'm working on this, 
I can then check *Messages* to be sure my new code ran and did the right 
thing.

I'll remove the Fmessage call before merging.

Previous Next

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