GNU bug report logs - #24585
25.1; avoid hack in ggtags.el to run compilation-auto-jump timer

Previous Next

Full log

Message #32 received at 24585 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Leo Liu <sdl.web <at> gmail.com>
Cc: 24585 <at> debbugs.gnu.org, monnier <at> IRO.UMontreal.CA
Subject: Re: bug#24585: 25.1;
 avoid hack in ggtags.el to run compilation-auto-jump timer
Date: Wed, 05 Oct 2016 13:25:45 +0300

> From: Leo Liu <sdl.web <at> gmail.com>
> Date: Wed, 05 Oct 2016 15:39:02 +0800
> Cc: 24585 <at> debbugs.gnu.org
> 
> On 2016-10-04 12:18 -0400, Stefan Monnier wrote:
> > That would explain why you want to remove the buffer from specific
> > windows (i.e. hide the buffer), but not why you need to kill it.
> 
> The buffer is not needed by ggtags so kill was chosen. I could change it
> to not kill but this won't fix the crux of the issue i.e.
> 
>   If compilation-auto-jump is run after cleanup it will mess up things
>   for example pop up windows.

Instead of adding another timer, and then dealing with their order
issues, is it possible to reuse the same time for both jobs?  IOW,
just _add_ the new/additional function you need to be done to whatever
the single timer does.  If you do that, you get to control the order
in which things are done by the single timer, because you write the
code of the timer function(s).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.