From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: RFC on enhancement for org-cancel-clock with no active clock Date: Mon, 4 Jan 2010 15:39:19 +0100 Message-ID: <10D58067-43B6-405A-A8F6-8A5F4C74016D@gmail.com> References: <20091218114219.GI5666@atlantic.linksys.moosehall> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NRo5g-0005tU-BF for emacs-orgmode@gnu.org; Mon, 04 Jan 2010 09:39:28 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NRo5b-0005t2-LU for emacs-orgmode@gnu.org; Mon, 04 Jan 2010 09:39:27 -0500 Received: from [199.232.76.173] (port=52371 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NRo5b-0005sz-HR for emacs-orgmode@gnu.org; Mon, 04 Jan 2010 09:39:23 -0500 Received: from mail-ew0-f224.google.com ([209.85.219.224]:50545) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NRo5a-0004nt-UV for emacs-orgmode@gnu.org; Mon, 04 Jan 2010 09:39:23 -0500 Received: by ewy24 with SMTP id 24so18033724ewy.26 for ; Mon, 04 Jan 2010 06:39:21 -0800 (PST) In-Reply-To: <20091218114219.GI5666@atlantic.linksys.moosehall> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Adam Spiers Cc: org-mode mailing list On Dec 18, 2009, at 12:42 PM, Adam Spiers wrote: > 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. Hi Adam, Hmm, no, I find this too error-prone. People might use org-clock-cancel as a lazy way to make sure that no clock is running, and in this way remove the most recent clock by accident. Sorry, this request does not make it... :-) - Carsten > > Thanks, > Adam > > > _______________________________________________ > 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 - Carsten