XEmacs 21.5 and dired-gets-current-buffer-wrong bug
kehoea at parhasard.net
Tue May 23 12:59:05 EDT 2006
Ar an tríú lá is fiche de mí Bealtaine, scríobh tbennett at nvidia.com:
> > I have tried to debug this in e-lisp but I have failed. I need a good
> > debug idea. Anyone who has an idea how to track this down?
Mats, try updating to a version of the cc-mode package more recent than June
2005, and check if you still have the problem.
> Wow, so someone else has seen this too.
> I first ran into this in 21.5.20 (ref: m37jiop84i.fsf at uh-oh.nvidia.com)
> It seemed to be triggered by lazy-lock but I couldn't figure out
> why. Eventually I tracked it down enough to generate the patch
> below which avoided the problem without ever figuring out what
> was really happening.
The pre-idle-hook code doesn’t save-excursion, so any errors in it after the
current buffer has been changed result in the current buffer getting out of
sync. If you want to debug this sort of problem, try something like
replacing each function in pre-idle-hook with one which calls the function,
catching any error thrown, and backtracing on it.
Aidan Kehoe, http://www.parhasard.net/
More information about the XEmacs-Beta