emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim O'Callaghan <timo@dspsrv.com>
To: emacs-orgmode@gnu.org
Subject: Re: Was: Feedback on Scheduling? - How do you use yours?
Date: Thu, 18 May 2006 11:24:58 +0200	[thread overview]
Message-ID: <20060518092458.GB1800@ELSAMSW37164> (raw)
In-Reply-To: <c5eb420b0605170659l24ed2d78w4674b1ab6f05e81f@mail.gmail.com>

On Wed, May 17, 2006 at 03:59:58PM +0200, Kevin Coates wrote:
> >> Yep - I need to make sure that the headline has enough info so 
> >that when
> >> printed onto the HPDA I can understand/recall what it relates to.
> 
> I'm also using a perl script to turn my org file of
> * ProjectName    :Project:
> ** NextAction     :Context1:
> ** AnotherNextAction     :Context2:
> 
> into
> (i) a list of Projects (ie all items tagged with :Project:); and
> (ii) individual pages for each :context: tags with a list of
> corresponding next actions
> 
> One way that helps me remember what the next action is about is to
> append [ProjectName] to the next action so the output is:
> 
> Context
> - NextAction [ProjectName]
> 

I like the :Project: TAG idea, i'm going to start using that one
myself. Any chance you could post the perl script for those
of us who are interested?

> >Do you have any interesting tools to help the weekly review?
> 
> Only thing I've come up with so far is to generate a list of Projects
> (identified by the :Project: tag) which have no next actions (ie 
> where
> the next item in the org outline also has a :Project: tag.
> 
> Also on the list of projects I'm printing them as
> ProjectName [number of next actions]
> which helps me see where projects have a lot of stuff building up
> 
> It's all fairly rudimentary at the moment, particularly as I'm using
> this as a way to learn perl - I'm a lawyer not a programmer ;-) - but
> I'm having fun.
> 

Perl is surprising like that :) 

I also like this idea, Its like a management summary on my
performance. A report to myself on how well i'm doing on my projects
and next actions.

> >how do you implement your tickler file?
> 
> So far I don't have one.  I have been thinking about a separate
> "reminders" file with the format:
> StartDate, DueDate, NextAction :context:
> Then amending the perl script to parse this file as well so that any
> nextactions whose startdate is on or before today also get included 
> in
> the context lists generated above.
> 

I've been using a folder and my Calendar. A 'memo' set on the
appropriate date. Its not integrated into org mode, but it seems to be
working. I'm not sure if its idea yet, but i'm sticking with it for
the moment, as i want to try and avoid as much yak shaving as i can.

Tim.

  reply	other threads:[~2006-05-18  9:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16  8:26 Feedback on Scheduling? Carsten Dominik
2006-05-16 17:19 ` Pete Phillips
2006-05-16 18:43   ` Tim O'Callaghan
2006-05-16 19:49     ` Pete Phillips
2006-05-16 21:20       ` Was: Feedback on Scheduling? - How do you use yours? Tim O'Callaghan
2006-05-17  7:41         ` Pete Phillips
2006-05-17  8:10           ` Carsten Dominik
2006-05-17 10:04           ` Tim O'Callaghan
2006-05-17 13:59             ` Kevin Coates
2006-05-18  9:24               ` Tim O'Callaghan [this message]
2006-05-18 11:14                 ` Kevin
2006-05-17  9:15   ` Feedback on Scheduling? David Emery
2006-05-17  9:14     ` Carsten Dominik

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=20060518092458.GB1800@ELSAMSW37164 \
    --to=timo@dspsrv.com \
    --cc=emacs-orgmode@gnu.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).