|
From: | Leo Liu |
Subject: | bug#24585: 25.1; avoid hack in ggtags.el to run compilation-auto-jump timer |
Date: | Mon, 03 Oct 2016 11:01:02 +0800 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/25.1 (macOS 10.12) |
On 2016-10-02 16:35 -0400, Stefan Monnier wrote: > IIUC this patch just changes the ordering for same-time timers. > Relying on either ordering is itself a hack. We need a better solution. If you eval (progn (run-with-timer 0 ...) ; timer 1 (run-with-timer 0 ...)) ; timer 2 you expect timer 1 to be triggered first, no? > What are those two timers whose relative execution order matters? > Why do they care in which order they're run? The first timer is compilation-auto-jump which is installed (by compile) at the start of compilation. The second timer is a cleanup timer which is installed (by ggtags) when compilation finishes and there is 0 or 1 match. The second timer kills the buffer (among other things) that the first timer depends on. Leo
[Prev in Thread] | Current Thread | [Next in Thread] |