[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Orgmode] Re: org-clock-idle-time resolving dialogues seem to stack
From: |
David Maus |
Subject: |
Re: [Orgmode] Re: org-clock-idle-time resolving dialogues seem to stack up for each passed idle time period |
Date: |
Sun, 27 Feb 2011 17:37:57 +0100 |
User-agent: |
Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Gojō) APEL/10.8 Emacs/23.2 (i486-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
Hi Rainer,
At Mon, 24 Jan 2011 14:41:15 +0100,
Rainer Stengele wrote:
> >
> > this still bugs me. After leaving idle my emacs for some time longer
> > than the configured idle time I have to apply answers to the idle-time
> > dialogue several times. I cannot simply press "j" to jump to the open clock
> > but
> > have to press "j" an unknown many times, mostly ending up with one or more
> > "j"
> > characters at the point I am being jumped to finally...
> >
> > Looks like I am the only one using this feature?
> >
> > Anybody has an idea?
I couldn't reproduce this problem neither with
Org-mode version 7.4 (release_7.4.509.g99aa5)
on
GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
of 2010-12-11 on raven, modified by Debian
nor on
GNU Emacs 23.2.1 (i386-mingw-nt6.1.7600)
of 2010-05-08 on G41R2F1
I had set `org-clock-idle-time' to 1, left the computer for a while
and when I came back there was just one clock resolving prompt
waiting.
Did you check if this problem occurs on emacs -q and just loading Org
mode w/o any configuration?
My preliminary conclusion on this issue: Org uses a timer object to
trigger the prompt -- if you are prompted multiple times this
would/could indicate that there are multiple timers for idle clock
resolving.
Can you verifiy this by checking the value of `timer-list' (C-h v
timer-list RET)?
Best,
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... address@hidden
Email..... address@hidden
pgp3sBJc0SzKK.pgp
Description: PGP signature
- Re: [Orgmode] Re: org-clock-idle-time resolving dialogues seem to stack up for each passed idle time period,
David Maus <=