From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bernt Hansen <bernt@norang.ca>
Subject: Re: clock in from last clock out
Date: Mon, 14 Jun 2010 19:27:21 -0400
Message-ID: <874oh52o12.fsf@gollum.intra.norang.ca>
References: <AANLkTinMfkrJ4OHzUfzsNOuXq5d9sfIPZcqkcgeV9WMH@mail.gmail.com>
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 [140.186.70.92] (port=58506 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OOJ3u-0002Cz-C0
	for emacs-orgmode@gnu.org; Mon, 14 Jun 2010 19:27:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <bernt@norang.ca>) id 1OOJ3s-0007N7-TR
	for emacs-orgmode@gnu.org; Mon, 14 Jun 2010 19:27:26 -0400
Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:51522)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <bernt@norang.ca>) id 1OOJ3s-0007N1-Ro
	for emacs-orgmode@gnu.org; Mon, 14 Jun 2010 19:27:24 -0400
In-Reply-To: <AANLkTinMfkrJ4OHzUfzsNOuXq5d9sfIPZcqkcgeV9WMH@mail.gmail.com>
	(Buck Brody's message of "Mon\, 14 Jun 2010 15\:37\:03 -0700")
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/archive/html/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: buckbrody@gmail.com
Cc: emacs-orgmode <emacs-orgmode@gnu.org>

Buck Brody <buckbrody@gmail.com> writes:

> Is there a way to clock in from the time that I most recently clocked
> out.  I often find that I finish something, clock out, and then start
> something new without remembering to clock back in.

I'm not aware of any existing clocking code functionality that does what
you describe.  I used to get around this by making clocking in and
clocking out actions completely manual so even if I mark a task done the
clock continues until I explicitly clock in something else.  This helped
me build a good habit of clocking in stuff on time.

Now I have a new setup[*1*] that automatically clocks in the default task
whenever org normally clocks out.  It doesn't sound like this is really
what you are looking for though.  In my case I would clock in the new
task and manually move the completed clock line from the default task to
the new task in this situation.

-Bernt


[*1*] http://doc.norang.ca/org-mode.html#ClockSetup