emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: William Denton <wtd@pobox.com>,
	Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: An Org-based productivity tool
Date: Wed, 10 Oct 2018 13:45:25 -0700	[thread overview]
Message-ID: <CAJcAo8tmOgn6mgThpiMyCaahPSwmVOcz9nVhME94Wb3-mv4_PQ@mail.gmail.com> (raw)
In-Reply-To: <87h8ht8sx1.fsf@mbork.pl>

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.

On 10/10/18, Marcin Borkowski <mbork@mbork.pl> wrote:
>
> On 2018-10-10, at 18:50, William Denton <wtd@pobox.com> wrote:
>
>> On 10 October 2018, Marcin Borkowski wrote:
>>
>>> I am making an Org-mode-based tool to help boost my productivity.
>>> ...
>>> - is anyone interested in something like this?
>>
>> I am---I'd love to see what you come up with.  I'm doing something
>> similar, but much less fancy, with clock tables and some R:
>>
>> https://www.miskatonic.org/2017/11/16/clocktableii/
>>
>> I need to do one more post about that to wrap it up.  It's working
>> well for me, but warnings about not being clocked in to something, and
>> better understanding of what I'm doing based on headings or tags,
>> would be useful.
>
> Thanks for your kind words!
>
> It's not that fancy (yet?), but has one big advantage over clock tables:
> it updates dynamically (using org-clock-out-hook), so it's fast.  Also,
> as you could see, it does some simple calculations.
>
> And for the record: it's based on properties, not tags - but that is
> a minor issue.
>
> Best,
>
> --
> Marcin Borkowski
> http://mbork.pl
>
>


-- 
The Kafka Pandemic: <http://thekafkapandemic.blogspot.com>

The disease DOES progress. MANY people have died from it. And ANYBODY
can get it at any time.

"You’ve really gotta quit this and get moving, because this is murder
by neglect." ---
<http://www.meaction.net/2017/02/03/pwme-people-with-me-are-being-murdered-by-neglect>.

  reply	other threads:[~2018-10-10 20:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 16:15 An Org-based productivity tool Marcin Borkowski
2018-10-10 16:50 ` William Denton
2018-10-10 20:10   ` Marcin Borkowski
2018-10-10 20:45     ` Samuel Wales [this message]
2018-10-11 13:16       ` Roland Everaert
2018-10-11 13:25         ` Ihor Radchenko
2018-10-11 13:44           ` Roland Everaert
2018-10-11 13:56             ` Ihor Radchenko
2018-10-11 20:05         ` Samuel Wales
2018-10-11 20:05           ` Samuel Wales
2018-10-14  8:08       ` Marcin Borkowski
2018-10-16 21:04         ` Samuel Wales
2018-10-29  9:05           ` Marcin Borkowski
2018-10-11  8:58 ` Ihor Radchenko
2018-10-14  8:22   ` Marcin Borkowski
2018-10-11 14:03 ` Bingo
2018-10-11 14:57   ` Peter Neilson
2018-10-11 15:08     ` Ihor Radchenko
2018-10-14  8:19       ` Marcin Borkowski
2018-10-14  8:19     ` Marcin Borkowski
2018-10-27  7:38     ` stardiviner
2018-10-28  1:24       ` Samuel Wales
2018-10-29  9:19         ` Marcin Borkowski
2018-10-29 21:03           ` Samuel Wales
2018-10-14  8:15   ` Marcin Borkowski
2018-10-16 20:39 ` Adam Porter
2018-10-16 21:43   ` Sacha Chua
2018-10-27  7:41     ` stardiviner
2018-10-29  9:17     ` Marcin Borkowski
2018-10-29 12:31       ` Sacha Chua
2018-10-29 17:17         ` Marcin Borkowski
2018-10-25  9:45 ` Ihor Radchenko
2018-10-29  9:08   ` Marcin Borkowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJcAo8tmOgn6mgThpiMyCaahPSwmVOcz9nVhME94Wb3-mv4_PQ@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@mbork.pl \
    --cc=wtd@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).