🚀 go-pugleaf

In vm-7.18 any errors which occur while vm-retrieved-spooled-mail-hook
functions run are not handled very gracefully.

It seems as though the INBOX buffer is unchanged even though the
retrieved messages have indeed been appended to it.  This is no doubt
because vm-assimilate-new-messages never gets called.

I made the following note about this issue in my sources:

Index: vm-folder.el
===================================================================
RCS file: /cvs/elisp/vm6/vm-folder.el,v
retrieving revision 1.1.1.20
diff -c -c -r1.1.1.20 vm-folder.el
*** vm-folder.el	23 Nov 2003 20:07:05 -0000	1.1.1.20
--- vm-folder.el	5 Dec 2003 03:21:38 -0000
***************
*** 3739,3744 ****
--- 3740,3751 ----
  	(setq vm-spooled-mail-waiting nil)
  	(intern (buffer-name) vm-buffers-needing-display-update)
  	(vm-update-summary-and-mode-line)
+ 	;; XXX if an error is signaled during run-hooks then the user won't see
+ 	;; the new message even though they are there!  The problem seems to be
+ 	;; similar to the one above with retrival-function.  The solution
+ 	;; though may simply be to ignore the error and go on to assimilate,
+ 	;; hoping that the errant hook function didn't do anything destructive
+ 	;; that can't be undone....  There's always vm-keep-crash-boxes too.
  	(if got-mail
  	    (run-hooks 'vm-retrieved-spooled-mail-hook))
  	(and got-mail (vm-assimilate-new-messages t))))))

-- 
						Greg A. Woods

+1 416 218-0098                  VE3TCP            RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>          Secrets of the Weird <woods@weird.com>