Hi guys, see below a problem from one of our XEmacs-users who is having trouble with autoloads. In the revision 627:
http://bazaar.launchpad.net/~vm/vm/8.0.x/revision/627 I have added autoload declarations for a few functions that were known to need them. This definitely cures the problem for GNU Emacs. It is possible that XEmacs needs some other treatment that I don't know about. Do you have an idea what might be going wrong? Cheers, Uday ------- start of forwarded message (RFC 934 encapsulation) ------- MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: <[email protected]> Reply-To: Bug 492117 <[email protected]> X-Launchpad-Bug: product=viewmail; status=New; importance=Undecided; assignee=None; X-Launchpad-Bug: product=vm; milestone=8.0.14; status=Confirmed; importance=High; [email protected]; X-Launchpad-Bug-Private: no X-Launchpad-Bug-Security-Vulnerability: no X-Launchpad-Bug-Commenters: lovell-hp reddyuday References: <[email protected]> <[email protected]> Message-Id: <[email protected]> X-Launchpad-Message-Rationale: Assignee Errors-To: [email protected] Precedence: bulk X-Generated-By: Launchpad (canonical.com); Revision="None"; Instance="initZopeless config overlay" X-Launchpad-Hash: 74a473946f3984ccb9f3bfa44662ef6516a464be From: Matthew Lovell <[email protected]> To: [email protected] Subject: [Bug 492117] Re: vm-8.0.13 mapvector possibly collides with xemacs built-in function Date: Fri, 04 Dec 2009 16:44:59 -0000 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 =3D> High > = > ** Changed in: vm > Milestone: None =3D> 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 bug assignee. 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 a= ppears 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 up= graded 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. N= evertheless, it would seem unwise to defun a duplicate of a built-in functi= on. ------- end ------- _______________________________________________ Mailing list: https://launchpad.net/~vm Post to : [email protected] Unsubscribe : https://launchpad.net/~vm More help : https://help.launchpad.net/ListHelp
