From: Rainer Stengele <rainer.stengele@diplan.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-clock-idle-time resolving dialogues seem to stack up for each passed idle time period
Date: Thu, 07 Oct 2010 10:46:47 +0200 [thread overview]
Message-ID: <4CAD88F7.5010002@diplan.de> (raw)
In-Reply-To: <i3gdvg$mk1$1@dough.gmane.org>
Am 06.08.2010 09:35, schrieb Rainer Stengele:
> hi all,
>
> having set org-clock-idle-time to 15 minutes the dialogue to resolve the idle time shows correctly after 15 minutes of idle time.
> Many times I simply press "j" just to jump to the running clock.
>
> What I experience is that I have to press "j" several times until the dialogue gets finally closed.
> It looks like the resolving dialogues are stacking up, one for each org-clock-idle-time period that has passed.
>
> Can anybody confirm this - well - bug?
>
>
> Rainer
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
Hi all,
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?
Rainer
next prev parent reply other threads:[~2010-10-07 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 7:35 org-clock-idle-time resolving dialogues seem to stack up for each passed idle time period Rainer Stengele
2010-10-07 8:46 ` Rainer Stengele [this message]
2011-01-24 13:41 ` Rainer Stengele
2011-02-27 16:37 ` David Maus
2011-02-28 13:31 ` Rainer Stengele
2011-03-03 14:02 ` Rainer Stengele
2011-03-06 18:16 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CAD88F7.5010002@diplan.de \
--to=rainer.stengele@diplan.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).