** Changed in: vm
Status: Confirmed => Fix Committed
** Also affects: vm/8.0.x
Importance: Undecided
Status: New
** Also affects: vm/trunk
Importance: High
Assignee: Uday Reddy (reddyuday)
Status: Fix Committed
** Changed in: vm/8.0.x
Status: New => Fix Committed
** Changed in: vm/8.0.x
Milestone: None => 8.0.14
** Changed in: vm/trunk
Milestone: 8.0.14 => 8.1.0-beta
** Changed in: vm/8.0.x
Importance: Undecided => High
** Changed in: vm/8.0.x
Assignee: (unassigned) => Uday Reddy (reddyuday)
--
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: Fix Committed
Status in VM 8.0.x series: Fix Committed
Status in VM trunk series: Fix Committed
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
