show-wspace.el fontlock problem
Neal Becker
ndbecker2 at gmail.com
Tue Feb 26 08:06:29 EST 2008
Stephen J. Turnbull wrote:
> Neal Becker writes:
>
> > Sort of works, but I'm getting millions of messages:
> > Fontifying region...(invalid-function 0)
> >
> > Strangely, setting debug-on-error doesn't seem to trap the message.
>
> If it were a debuggable error, I have to admire your stamina. You
> only get one error per command, so you tried it millions of times! :-)
>
> Now, debug-on-error hooks into the process *later* than condition-case
> does, so if the error is handled in code you'll never see it. What
> you need here is debug-on-signal, which drops you into the debugger
> before condition-case gets its hands on it.
>
> You could also just look for condition-cases in the code.
It appears that show-wspace.el itself isn't causing a problem. I manually
loaded it and activated without error. I think the hooks I added to my
init.el are causing the problem:
;(add-hook 'python-mode-hook 'show-ws-highlight-tabs)
;(add-hook 'font-lock-mode-hook 'show-ws-highlight-trailing-whitespace)
More information about the XEmacs-Beta
mailing list