Back out a previous change to make SAVE-RESOURCE `gracefully' handle

failures.  Irrevocably losing users' mail is not graceful.  Use `M-x
revert-buffer RET' first if you really need to kill the buffer.

diff --git a/src/imail/imail-file.scm b/src/imail/imail-file.scm
index 2b07470e1e7391829805ade6578c074365094c56..55fbb77405eb616e74f16afce12d0e133c55ae9b 100644 (file)
--- a/src/imail/imail-file.scm
+++ b/src/imail/imail-file.scm
@@ -406,21 +406,9 @@ USA.
             (and (eq? status 'BOTH-MODIFIED)
                  (imail-ui:prompt-for-yes-or-no?
                   "Disk file has changed since last read.  Save anyway"))))
-       (call-with-current-continuation
-        (lambda (k)
-          (bind-condition-handler (list condition-type:error)
-              (lambda (condition)
-                ;; Can this be done in a pop-up buffer?  It doesn't
-                ;; work just to use IMAIL-UI:PRESENT-USER-ALERT
-                ;; because that futzes with the kill-buffer hooks.
-                (imail-ui:message
-                 (call-with-output-string
-                   (lambda (output-port)
-                     (write-condition-report condition output-port))))
-                (k #f))
-            (lambda ()
-              (synchronize-file-folder-write folder write-file-folder)
-              #t))))))
+       (begin
+        (synchronize-file-folder-write folder write-file-folder)
+        #t)))
 
 (define-generic write-file-folder (folder pathname))