bug#24959: 26.0.50; cancel-timer: void-variable timer

[Oleg Sivokon]

Lars,
I'll need to experiement with this then. My hunch is that when this
happens inside condition-case, the things don't work exactly the same.
I'll try to come up with a minimal example for the problem.

On Thu, Nov 17, 2016 at 8:09 PM, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Oleg Sivokon <oleg.sivokon@elastifile.com> writes:
>
>> No, I don't use lexical bindings in this code. But, my point is that
>> the behavior of setq used to be to make variable special (i.e.
>> universaly accessible, like global, except it can be let-bound
>> temporarily), which it doesn't seem to do anymore.
>
> It does for me.
>
> [...]
>
>>>> (setq timer (run-at-time 1 1 (lambda () (cancel-timer timer)))
>
> You've forgotten an end parentheses there.  If I add one and eval the
> form, it works fine for me.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no