Subject: bug#9574: closed (Re: bug#9574: data-loss with --batch: ignored write failure)

From: [email-masked] (GNU bug Tracking System)
Date: Fri, 23 Sep 2011 10:00:02 +0000

Your bug report

#9574: data-loss with --batch: ignored write failure

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
9574: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9574
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#9574: data-loss with --batch: ignored write failure
From: Andreas Schwab <[email-masked]>
To: Jim Meyering <[email-masked]>
Cc: [email-masked]
Date: Fri, 23 Sep 2011 11:58:44 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

Fixed.

Andreas.

-- 
Andreas Schwab, [email-masked]
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Subject: data-loss with --batch: ignored write failure
From: Jim Meyering <[email-masked]>
To: [email-masked]
Date: Thu, 22 Sep 2011 16:39:04 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

This should diagnose the write failure and exit nonzero:

    emacs --version > /dev/full

Currently (latest from bzr trunk as of yesterday),
emacs exits 0 (successfully) and gives no diagnostic.
Obviously that doesn't matter too much, but this next one
can easily cause real trouble:

    $ emacs --batch --eval '(print "important")' > /dev/full && echo FAIL
    FAIL

I.e., the write fails and emacs fails to report that failure.

That means anything written via --batch to standard output may
be corrupted or incomplete, and emacs will still exit successfully.