Re: "Use font-lock-support-mode rather than calling lazy-lock-mode"

[ishikawa]

Jason Rumney wrote:
> ishikawa wrote:
>> So I am wondering. Is there a way to print the
>> calling function of turn-on-lazy-lock
>> a la the following code snippet?
>>   
> (backtrace)

Dear Mr. Jason Rumney,

Thank you for pointing out the existence of "backtrace" function.

Before receiving your e-mail, I figured out how to place a breakpoint
on lisp functions using "edebug" package.
By doing so, I could enter debug mode when a particular function
was called. And from there, I could take a look at the stack backtrace and
figured out where the problems occured. It was inside one of the
helper function for old VM mail package, which I probably modified myself.
By modifing the code so that it is no longer called when emacs versio 22 is
running, I no longer get the warning for the course of the day's work.
(And jit-lock seems to take care of the situation very well.)

About 30 minutes ago, I tried (backtrace).
It seems to me that to obtain a useful output and
not interfering the normal operation of various modes,
I need to create a separate buffer, say "*backtrace*" and then
dump the contents of the output of (backtrace) there, and
then resume the normal operation.
(It seems to me that "edebug" package just does that, but I have not figured out
exactly how to do it.)

Without such a trick, backtrace seems to create output *somewhere* and
normal operations such as electric-dired and others don't work anymore.

Creating such a trick in a short time
is a little beyond the hobbyiest emacs-lisp user like me although
I have used Emacs more than 20 years now...

So if I have time in the next several weeks to investigate, I will
come up with the code snippet to obtain useful output from "(traceback)".
In the meantime, my original problem is solved using "edebug" package.

Thank you again for your help.

Happy Hacking!

Chiaki Ishikawa