From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adam Spiers <orgmode@adamspiers.org>
Subject: RFC on enhancement for org-cancel-clock with no active clock
Date: Fri, 18 Dec 2009 11:42:19 +0000
Message-ID: <20091218114219.GI5666@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 1NLbE9-0006zY-PF
	for emacs-orgmode@gnu.org; Fri, 18 Dec 2009 06:42:33 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NLbE5-0006v7-1P
	for emacs-orgmode@gnu.org; Fri, 18 Dec 2009 06:42:32 -0500
Received: from [199.232.76.173] (port=49279 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NLbE4-0006us-O6
	for emacs-orgmode@gnu.org; Fri, 18 Dec 2009 06:42:28 -0500
Received: from vpn.id2.novell.com ([195.33.99.129]:35178
	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 1NLbE4-0007ft-70
	for emacs-orgmode@gnu.org; Fri, 18 Dec 2009 06:42:28 -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>

Currently org-cancel-clock just warns 'No active clock' when there is
no active clock.  Would it make sense to extend the behaviour in that
case so that it interactively prompts whether you would like to remove
the most recently active clock entry?  This would be a nice kind of
'undo' in the case where you clock out when you actually meant to
cancel the active clock.

Thanks,
Adam