Latest timer changes may be breaking external packages

Latest timer changes may be breaking external packages

[T.V Raman]

Specifically, It appears to break latest versions of hydra installed
from melpa like so:

one of the timers defined in hydra.el -- hydra-timeout-timer --  ends
up as a vector of length 9  and then ends up throwing an error as an
invalid timer; timer-create in a running emacs creates a timer of
length 10.


-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

Re: Latest timer changes may be breaking external packages

[Lars Ingebrigtsen]

"T.V Raman" <raman@google.com> writes:

> Specifically, It appears to break latest versions of hydra installed
> from melpa like so:
>
> one of the timers defined in hydra.el -- hydra-timeout-timer --  ends
> up as a vector of length 9  and then ends up throwing an error as an
> invalid timer; timer-create in a running emacs creates a timer of
> length 10.

I think this means that your Emacs needs a "make bootstrap".

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: Latest timer changes may be breaking external packages

[T.V Raman]

Will try that -- but why does that break a package that is installed
and was last compiled 6+ months ago?
Lars Ingebrigtsen writes:
 > "T.V Raman" <raman@google.com> writes:
 > 
 > > Specifically, It appears to break latest versions of hydra installed
 > > from melpa like so:
 > >
 > > one of the timers defined in hydra.el -- hydra-timeout-timer --  ends
 > > up as a vector of length 9  and then ends up throwing an error as an
 > > invalid timer; timer-create in a running emacs creates a timer of
 > > length 10.
 > 
 > I think this means that your Emacs needs a "make bootstrap".
 > 
 > -- 
 > (domestic pets only, the antidote for overdose, milk.)
 >    bloggy blog: http://lars.ingebrigtsen.no

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

--

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

Re: Latest timer changes may be breaking external packages

[Lars Ingebrigtsen]

"T.V Raman" <raman@google.com> writes:

> Will try that -- but why does that break a package that is installed
> and was last compiled 6+ months ago?

Because it was compiled then, and uses a macro from timer.el.

I've done further changes to timer.el that should make the changes
backwards-compatible so that the packages don't have to be recompiled
now.  Hopefully.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: Latest timer changes may be breaking external packages

[Kaushal Modi]

[-- Attachment #1: Type: text/plain, Size: 463 bytes --]

On Thu, Sep 2, 2021 at 9:59 PM T.V Raman <raman@google.com> wrote:

> Specifically, It appears to break latest versions of hydra installed
> from melpa like so:
>
> one of the timers defined in hydra.el -- hydra-timeout-timer --  ends
> up as a vector of length 9  and then ends up throwing an error as an
> invalid timer; timer-create in a running emacs creates a timer of
> length 10.
>

I noticed that too! It got fixed after I deleted and re-installed hydra.

[-- Attachment #2: Type: text/html, Size: 788 bytes --]