From: Marcin Borkowski <mbork@mbork.pl>
To: Samuel Wales <samologist@gmail.com>
Cc: William Denton <wtd@pobox.com>,
Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: An Org-based productivity tool
Date: Mon, 29 Oct 2018 10:05:55 +0100 [thread overview]
Message-ID: <87h8h55dho.fsf@mbork.pl> (raw)
In-Reply-To: <CAJcAo8tN+cAd+r0Qvv1ttV58-FEbQZixEwczDPMGvxRkN7eQFw@mail.gmail.com>
On 2018-10-16, at 23:04, Samuel Wales <samologist@gmail.com> wrote:
> On 10/14/18, Marcin Borkowski <mbork@mbork.pl> wrote:
>> 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).
>
> hm, it doesn't seem so to me. what do you mean by 2 or more related
> to the same file? a file can have any number of clocking tasks, and
> you can manually clock any time you want which would suspend the
> automatic clocking until you clock out. [just sets a variable.]
>
> i guess it's just a matter of taste. i don't think i will do your
> level of clocking unless it is auytomatic.
As I said, it won't/can't work for me.
Assume I have a project with two tasks, A and B. Assume that the
project consists of many files, among others: main.js, utils.js,
main.css. Assume that task A involves editing files main.js and
main.css and task B - files main.js and utils.js.
Assuming I'm editing main.js, how can an automatic system (short of an
advanced AI) guess whether to clock A or B?
I found that it is way easier to train myself to clock in (it helps to
have a nice keybinding for that - F10 F10 for clocking in the last task,
F10 i for a classical clock history and F10 c for Counsel-based clock
history.
>> > (And I have this notification nagging me if I'm not clocking anything
>> for 2 minutes or more.)
>
> i'd get so distracted and thus annoyed by that notificaiton that it
> would be nuked into outer space. :]
The same with me - that's precisely the point. This nuke is called
`org-clock-in'. ;-)
Best,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2018-10-29 9:07 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
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 [this message]
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=87h8h55dho.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
--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).