Hi Matt, I just built 8.0.13 in xemacs and find that the auto- autoloads.el has the right autoload for vm-pine including vm-decode- postponed-mime-message. (see below)
Can you elaborate what you mean by "still having problems"? Cheers, Uday ;;;### (autoloads (vm-mail-to-fcc vm-mail-select-folder vm-mail-get-header-contents vm-mail-auto-fcc vm-mail-fcc vm-mail-priority vm-mail-notice-requested-upon-delivery-to vm-mail-return-receipt-to vm-continue-what-message-other-frame vm-continue-what-message-other-window vm-continue-what-message vm-postpone-message vm-decode-postponed-mime-message vm-reply-by-continue-postponed-message vm-continue-postponed-message vm-summary-function-p vm-summary-function-f) "vm-pine" "lisp/vm-pine.el") -- vm-8.0.13 mapvector possibly collides with xemacs built-in function https://bugs.launchpad.net/bugs/492117 You received this bug notification because you are a member of VM development team, which is the registrant for VM (defunct). Status in VM - Goto http://launchpad.net/vm for active development: New Status in VM (View Mail) for Emacs: Confirmed Bug description: vm-8.0.13 introduced a defun for mapvector in vm-folder. This definition appears to stomp upon the function built into xemacs already: `mapvector' is a built-in function (mapvector FUNCTION SEQUENCE) This became evident trying to invoke latex-mode on a buffer after having upgraded from vm-8.0.12 to vm-8.0.13. This resulted in an error saying that a mapvector usage had an incorrect argument. Changing vm-folder.el such that it defines and uses vm-mapvector appears to have fixed this behavior. I was attempting to revert this change to obtain a back trace of the error, but I am currently unable to reproduce the exact one I am experiencing. Nevertheless, it would seem unwise to defun a duplicate of a built-in function. _______________________________________________ Mailing list: https://launchpad.net/~vm Post to : [email protected] Unsubscribe : https://launchpad.net/~vm More help : https://help.launchpad.net/ListHelp
