vm team mailing list archive

[Matthew Lovell <lovell@xxxxxx>]

Hi Uday,

Uday Reddy writes:
 > Thanks very much, Matthew.  Sigh...  I have to do another release in
 > quick succession and withdraw 8.0.13.  Embarassing...
 > 
 > Can you help us about by testing pre-releases in XEmacs?

Certainly.

I find I'm also still having problems with auto-autoloads.el and

  vm-decode-postponed-mime-message

my solution currently is to copy auto-autoloads.el over to
vm-autoloads.el and add

  (provide 'vm-autoload)

at the tail.

Thanks,
  Matt


 > ** Changed in: vm
 >    Importance: Undecided => High
 > 
 > ** Changed in: vm
 >     Milestone: None => 8.0.14
 > 


-- 
Matthew Lovell
Hewlett-Packard

-- 
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.

Status in View Mail (aka VM) for Emacs: 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.