[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: jit-lock-antiblink-grace
From: |
Stefan Monnier |
Subject: |
Re: jit-lock-antiblink-grace |
Date: |
Fri, 11 Oct 2019 10:26:26 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
> At Stefan's request, I have reworked the implementation and
> cleaned up the feature, which is embodied in the jit-lock-antiblink-grace
> variable and want to land it on master if no-one objects.
No objection from me.
> BTW: I tried to force-push the cleaned-up version to the
> scratch/jit-lock-antiblink branch. It didn't work. Is force-pushing
> disabled in those branches? It didn't use to be, IIRC.
Force-pushing is disabled repository-wide. You can workaround it by
removing+pushing the branch, instead (this workaround can technically be
used on any branch, but of course we don't want it used elsewhere than
in scratch/* branches).
Stefan
- jit-lock-antiblink-grace, João Távora, 2019/10/10
- Re: jit-lock-antiblink-grace,
Stefan Monnier <=
- Re: jit-lock-antiblink-grace, Eli Zaretskii, 2019/10/12
- Re: jit-lock-antiblink-grace, João Távora, 2019/10/12
- Re: jit-lock-antiblink-grace, Juanma Barranquero, 2019/10/12
- Re: jit-lock-antiblink-grace, João Távora, 2019/10/12
- Re: jit-lock-antiblink-grace, Juanma Barranquero, 2019/10/12
- Re: jit-lock-antiblink-grace, João Távora, 2019/10/12
- Re: jit-lock-antiblink-grace, Juanma Barranquero, 2019/10/12
- Re: jit-lock-antiblink-grace, Eli Zaretskii, 2019/10/12
- Re: jit-lock-antiblink-grace, Stefan Monnier, 2019/10/12
- Re: jit-lock-antiblink-grace, Eli Zaretskii, 2019/10/12