GNU bug report logs - #9574
data-loss with --batch: ignored write failure

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Jim Meyering <jim <at> meyering.net>
Subject: bug#9574: closed (patch installed)
Date: Sun, 04 Nov 2012 17:23:03 +0000

[Message part 1 (text/plain, inline)]

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 9574 <at> debbugs.gnu.org.

-- 
9574: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9574
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: 9574-done <at> debbugs.gnu.org
Subject: patch installed
Date: Sun, 04 Nov 2012 09:19:07 -0800

I installed the patch for this into the Emacs trunk as bzr 110786
and am marking it as done.

[Message part 3 (message/rfc822, inline)]

From: Jim Meyering <jim <at> meyering.net>
To: bug-emacs <at> gnu.org
Subject: data-loss with --batch: ignored write failure
Date: Thu, 22 Sep 2011 16:39:04 +0200

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.

Previous Next

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