From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcin Borkowski <mbork@mbork.pl>
Subject: Re: An Org-based productivity tool
Date: Sun, 14 Oct 2018 10:08:58 +0200
Message-ID: <87sh199ch1.fsf@mbork.pl>
References: <87efcxaibq.fsf@mbork.pl>
	<alpine.DEB.2.02.1810101247440.611@shell.miskatonic.org>
	<87h8ht8sx1.fsf@mbork.pl>
	<CAJcAo8tmOgn6mgThpiMyCaahPSwmVOcz9nVhME94Wb3-mv4_PQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48348)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mbork@mbork.pl>) id 1gBbTq-0003bL-5d
	for emacs-orgmode@gnu.org; Sun, 14 Oct 2018 04:10:30 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mbork@mbork.pl>) id 1gBbTm-0004rz-Ay
	for emacs-orgmode@gnu.org; Sun, 14 Oct 2018 04:10:30 -0400
Received: from mail.mojserwer.eu ([195.110.48.8]:33970)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mbork@mbork.pl>) id 1gBbTk-0004ne-Bx
	for emacs-orgmode@gnu.org; Sun, 14 Oct 2018 04:10:24 -0400
In-reply-to: <CAJcAo8tmOgn6mgThpiMyCaahPSwmVOcz9nVhME94Wb3-mv4_PQ@mail.gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/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: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Samuel Wales <samologist@gmail.com>
Cc: William Denton <wtd@pobox.com>, Org-Mode mailing list <emacs-orgmode@gnu.org>


On 2018-10-10, at 22:45, Samuel Wales <samologist@gmail.com> wrote:

> auto-clocking might be interesting.
>
> there would be a concept of a dominating clocking entry similar to
> dominating file.  i.e. if where you are is not a clocking entry, go up
> until you find one that is.  if you find none at top level, you create
> a clock entry in the logbook there.
>
> if you switch buffers or move around, you clock out and in where you
> were and are.  every few minutes, you try to clock in where you are,
> or the dominating clocking entry.  this is done with timers.  idle
> time might go to a special clocking entry.
>
> or something like that.  the idea is that you don't have to remember
> to clock in and out.

That's an interesting idea I thought about some time ago.

But I decided it's not worth it.  Very complicated and unreliable (I
might have two or more clocking tasks related to the same file, for
example).

It's better to train oneself to remember about clocking, I guess.

(And I have this notification nagging me if I'm not clocking anything
for 2 minutes or more.)

Best,

--
Marcin Borkowski
http://mbork.pl