xretrace timer doesn't start

[Graeme]

In V26 beta 3 (and beta 2) the timer used by xretrace doesn't start when start_xretrace is called from definit.  V25 and earlier versions don't have this problem.  Sometimes if I call start_xretrace twice in the definit it will start.  Steps to load xretrace and test are in the attached pdf.  I have temporarily worked around this by making commands such as xretrace_cursor check if the timer is running and start it if not (it starts ok at this point) but I would like to have the timer running right from startup.

[Clark]

We will look into this

[Clark]

autosave.e is deleting/killing a timer by mistake.

Fixed for beta 4

I've attached a fix for beta 3 for this

[Clark]

I think the problem you are having with xgpinhere, is that when the editor is invoked, it's possible that it could already be 1. I suggest you initialize to 0 in your definit(). That will guarantee that it has the right value at startup.

[Graeme]

ah, I didn't think of it being initialization because it happened a long time after a restart, due to xretrace not starting.  Thanks and thanks for the timer fix.