Re: watching for variable assignment

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Nicolas Richard <theonewiththeevillook@yahoo.fr> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Jambunathan K <kjambunathan@gmail.com> writes:
>>
>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>>
>>>> I'm trying to somehow trigger a message or a backtrace whenever that
>>>> variable's value changes.
>>>
>>>
>>> You are looking for a "Write Breakpoint".  I haven't done much Elisp
>>> debugging.  Going by the docs, the following looks promising.
>>>
>>>     (info "(elisp) Global Break Condition")
>>
>> Hey thanks! That's a new one for me, and does indeed look promising.
>> I've set edebug-global-break-condition to (eq nnimap-split-fancy nil),
>> and will see what happens. It says it tests the expression at every
>> "stop point". I haven't explicitly set any stop points; hopefully
>> they are set automatically, since the whole point of this is that I
>> don't know where to check for the assignment.
>
> I guess it requires the relevant code to be instrumented for edebug,
> otherwise edebug won't do anything.

Yeah, that's what I'm realizing. A bit of a pain, but I guess I can try
to make it work... I wish there was a command that said "instrument
gnus-group-get-new-news and everything it calls", since that seems to be
where the evil happens. Anyway, I'll futz with it.