emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mycroft Jones <mycroft@reactor-core.org>
To: Melleus <melleus@openmailbox.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: orgmode for many continuous tasks?
Date: Tue, 26 Sep 2017 10:36:36 -0700	[thread overview]
Message-ID: <20170926173636.GA12628@reactor-core.org> (raw)
In-Reply-To: <87r2utvjjo.fsf@openmailbox.org>

On Tue, Sep 26, 2017 at 01:30:35PM +0300, Melleus wrote:
>> The answer is obvious: a clipboard! It's rugged and inexpensive.
>>
>> I've actually done this a few times, when I've been using Org to
>> organize event management and was out of the office all day long.
>> Printed out my daily agenda in the morning, made notes on the clipboard
>> throughout the day, and entered changes into the computer at the end of
>> day.

Yes, I said the same to Peter in private email.  And, if you print off your
list, it gets depressing because it is SO long, longer than you could hope to
accomplish in a day.  That is why I'd like the algorithm to take into account
the time budget, and only put on a number of things that add up to 8 hours.
So, some items are done in 1/2 hour chunks, others in 2 hour chunks, all good.
That way you have a daily task list and can feel good accomplishment if you
clear up your list for the day.

>Maybe it's a bit overhead, but anyway. You can use org-caldav-sync to sync the
>todos with local owncloud (or other caldav) server and use some phone/tablet's
>calendar to sync with owncloud to have your tasklist with you on the run and
>you can use it for capturing todos also, as the two-way sync is no problem for
>org-caldav-sync.

When you're up on a roof, or driving a tractor, or shearing a sheep, a cell
phone can be destroyed very quickly.  Last thing you need is it dropped into
the mud and stepped on by a heavy ungulate.  Clipboard is cheap, and you can
always print out your list again.  Getting in the habit of being away from the
computer is good.  Getting in the habit of reviewing the days events at the end
of it is also good.

Mycroft

  reply	other threads:[~2017-09-26 17:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25  7:21 orgmode for many continuous tasks? Mycroft Jones
2017-09-25 11:58 ` Peter Neilson
2017-09-25 12:07   ` Neil Jerram
2017-09-25 16:34   ` Mycroft Jones
2017-09-25 22:08   ` Tim Cross
2017-09-26  0:40     ` Eric Abrahamsen
2017-09-26 10:30       ` Melleus
2017-09-26 17:36         ` Mycroft Jones [this message]
2017-09-26 18:56           ` Eric Abrahamsen
2017-09-27 16:14           ` Melleus
2017-09-27 17:02             ` Mycroft Jones
2017-09-27 17:13               ` Peter Neilson
2017-09-26 19:41       ` Eduardo Mercovich
2017-09-25 20:28 ` Mikhail Skorzhinskii
2017-09-25 20:34   ` Mikhail Skorzhinskii
2017-09-27 23:24 ` Bob Newell
2017-09-28  5:48   ` Eric S Fraga
2017-10-03 23:04     ` Mycroft Jones
2017-10-04  5:38       ` Eric S Fraga

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=20170926173636.GA12628@reactor-core.org \
    --to=mycroft@reactor-core.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=melleus@openmailbox.org \
    /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).