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: Paul Eggert <eggert <at> cs.ucla.edu>
To: Jim Porter <jporterbugs <at> gmail.com>, Eli Zaretskii <eliz <at> gnu.org>
Cc: mail <at> daniel-mendler.de, 79079 <at> debbugs.gnu.org
Subject: bug#79079: 31.0.50; Piped command output is sometimes lost in Eshell
Date: Thu, 24 Jul 2025 11:50:29 -0700

On 2025-07-24 10:05, Jim Porter wrote:
> Could there be a time when we get an error from 'process-send-string', 
> but we can try calling it again later?

Not if it's an EPIPE failure. EPIPE means the connection is permanently 
down.

I don't offhand know of any failure for writing to a pipe where retrying 
would make sense, other than EAGAIN and EWOULDBLOCK which the code is 
already dealing with.

Can process-send-string write to other file types? If so, there are 
other possibilities where retrying might work, e.g., ENOSPC for write to 
a regular file, ENETDOWN for sendto to a network socket.

Previous Next

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