vm team mailing list archive
-
vm team
-
Mailing list archive
-
Message #00122
[Bug 492117] Re: vm-8.0.13 mapvector possibly collides with xemacs built-in function
Matt, I have put the release of 8.0.14 on the Launchpad project page.
Can you please verify that it works? -- Uday
** Changed in: vm/8.0.x
Status: Fix Committed => Fix Released
** Changed in: vm/trunk
Status: Fix Committed => In Progress
--
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: In Progress
Status in VM 8.0.x series: Fix Released
Status in VM trunk series: In Progress
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.