From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adam Spiers <orgmode@adamspiers.org>
Subject: resolving idle time after accidentally cancelling prompt
Date: Fri, 18 Dec 2009 11:26:42 +0000
Message-ID: <20091218112642.GG5666@atlantic.linksys.moosehall>
Reply-To: Adam Spiers <orgmode@adamspiers.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NLbNm-0006xz-DJ
	for emacs-orgmode@gnu.org; Fri, 18 Dec 2009 06:52:30 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NLbNh-0006wn-0T
	for emacs-orgmode@gnu.org; Fri, 18 Dec 2009 06:52:29 -0500
Received: from [199.232.76.173] (port=35849 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NLbNg-0006wg-OP
	for emacs-orgmode@gnu.org; Fri, 18 Dec 2009 06:52:24 -0500
Received: from vpn.id2.novell.com ([195.33.99.129]:47626
	helo=gwia-smtp.id2.novell.com) by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <aspiers@novell.com>) id 1NLbNg-0008Rv-Cl
	for emacs-orgmode@gnu.org; Fri, 18 Dec 2009 06:52:24 -0500
Content-Disposition: inline
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: org-mode mailing list <emacs-orgmode@gnu.org>

Hi there,

The `org-clock-idle-time' feature is really fantastic.  However I
occasionally miss the [(kK)eep (sS)ubtract (C)ancel] prompt in the
minibuffer and press another key which cancels it; then I have to run
org-resolve-clocks manually.  I can imagine a scenario where I
mistakenly thought that the window manager focus was in another
window, started typing, accidentally cancelled the prompt, and never
even noticed it was there in the first place - resulting in a
permanently dangling clock.  Would it be worth making this code
idiot-proof ...

    (if (or (null ch)
	    (not (memq ch '(?k ?K ?s ?S ?C))))
	(message "")

.. so that the only way to cancel the prompt is to press `C' ?  It
would also be nice if upon cancellation it did

  (message "Use `M-x org-resolve-clocks' to resolve dangling clocks at any time.")

Thanks,
Adam