emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten <quintfall@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-mode as an accountability system?
Date: Sat, 03 Mar 2012 19:56:15 +0100	[thread overview]
Message-ID: <87linh1pkg.fsf@googlemail.com> (raw)
In-Reply-To: CAE+_6TwoxB_+fFG2=xsCctBb2C3vx03sYk2q_o4VZ+nMpKMmdQ@mail.gmail.com

Peter Salazar <cycleofsong@gmail.com> writes:

Hi Peter, 
without claiming being an expert org-mode user, I had the following
thoughts when reading your post: 

> I have an accountability partner with whom I exchange daily "committed
> actions." Every morning, I e-mail him a list of the tasks I commit to
> completing that day. 

Why sending per email? Why not getting a free private(!) git repo (1GB)
at assembla.com and cooperatively work on one or several org file(s) in
that repo?

> When I complete a task, I mark it DONE. If I don't complete a task
> that day, I mark it @didnotdo and manually cut and paste it to the
> next day. 
> Every night, I send him a report of which actions I did and which ones
> I did not do. (I find I get so much more done since I started making
> daily commitments to someone other than myself.)
If you both work on the same file using git, the current state of
affairs will always be clear, as well as who did what at what time (and
pushed it to the repo). 

> 1. Given that I'm creating my daily task list manually, is there an
> easy way, when I mark a task @didnotdo, to automatically move it to
> the next day's list and change its state to @todo? 

When I have a TODO task in the agenda that I did not complete today, I
just change the date to tomorrow in the agenda using '>'. 
If you don't do that, it will appear anyway in the agenda as overdue


  reply	other threads:[~2012-03-03 18:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 18:22 org-mode as an accountability system? Peter Salazar
2012-03-03 18:56 ` Thorsten [this message]
2012-03-03 19:18   ` Peter Salazar
2012-03-03 20:25     ` John Hendy
2012-03-04 10:03       ` Jude DaShiell
2012-03-04 14:08 ` Memnon Anon
2012-03-05 11:44   ` Darlan Cavalcante Moreira
2012-03-09  2:17     ` Peter Salazar

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:

  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=87linh1pkg.fsf@googlemail.com \
    --to=quintfall@googlemail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).