emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#9574: closed (data-loss with --batch: ignored writ


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#9574: closed (data-loss with --batch: ignored write failure)
Date: Sun, 04 Nov 2012 17:23:02 +0000

Your message dated Sun, 04 Nov 2012 09:19:07 -0800
with message-id <address@hidden>
and subject line patch installed
has caused the debbugs.gnu.org bug report #9574,
regarding data-loss with --batch: ignored write failure
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
9574: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9574
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- 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.



--- End Message ---
--- Begin Message --- Subject: patch installed Date: Sun, 04 Nov 2012 09:19:07 -0800 User-agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
I installed the patch for this into the Emacs trunk as bzr 110786
and am marking it as done.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]