🚀 go-pugleaf

Todd Wilson wrote:
 > By default, the key "*" is mapped to vm-burst-digest, and the variable
 > vm-delete-after-bursting determines whether the original digest is
 > marked for deletion after bursting.  However, I prefer to burst
 > digests into a separate folder, so I have the following in my .vm:
 >
 >     (define-key vm-mode-map "*" 'vm-burst-digest-to-temp-folder)
 >
 > This has the advantage that quitting the temp folder is tantamount to
 > deleting all of the bursted messages at one time.  However, the
 > variable vm-delete-after-bursting no longer applies to the original
 > digest, whereas it seems that it should.

I can't speak for Kyle, but I suspect that this behavior is intentional
because the possibility of losing the digest's messages is much greater
than if they'd been burst to a real folder.  But if
vm-delete-after-bursting is set, perhaps vm-burst-digest-to-temp-folder
ought to at least ask, eh?  That's what this patch does, but I don't
know if it will work when bursting multiple digests at once, or when
bursting a digest from a virtual folder.

*** vm-7.18/vm-digest.el.orig	Sat May  3 15:31:52 2003
--- vm-7.18/vm-digest.el	Thu Feb 19 17:29:13 2004
***************
*** 708,713 ****
--- 708,720 ----
   		   (vm-rfc1153-burst-message m))
   		  (t (error "Unknown digest type: %s" digest-type)))
   	    (message "Bursting %s digest... done" digest-type)
+ 	    (and vm-delete-after-bursting
+ 		 (yes-or-no-p (format "Delete message %s? " (vm-number-of m)))
+ 		 (save-excursion
+ 		   (set-buffer start-buffer)
+ 		   ;; don't move message pointer when deleting the message
+ 		   (let ((vm-move-after-deleting nil))
+ 		     (vm-delete-message 1))))
   	    (setq mlist (cdr mlist)))
   	  (set-buffer-modified-p nil)
   	  (vm-save-buffer-excursion

-- 
Kevin Rodgers