Hello,

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

[...]
>
> Is there any reason to use this particular commit? If so, please add
> a comment in the definition. Otherwise, I suggest to stick to stable
> releases.
>

The main reason is the introduction of a handy defcustom in [0], and
less importantly other small typo/doc fixes, and lack of a tagged
release in about a year.

[0]: https://github.com/EricCrosson/unkillable-scratch/commit/26102d5434e47c77219fce76c255cafb69b8e222

I think it would be nice if our package included the customization, but
if there’s a strong preference over using a tagged release including in
this case, I’d be happy to send a v2 definition to use a tagged version,
and later inherit from it in my personal channel to make a -git version
including the feature for my own use.

What do you think?

>
> Regards,

Thanks,
amin