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: Fri, 23 Sep 2011 10:00:02 +0000

Your message dated Fri, 23 Sep 2011 11:58:44 +0200
with message-id <address@hidden>
and subject line Re: bug#9574: data-loss with --batch: ignored write failure
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: Re: bug#9574: data-loss with --batch: ignored write failure Date: Fri, 23 Sep 2011 11:58:44 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
Fixed.

Andreas.

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


--- End Message ---

reply via email to

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