From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim O'Callaghan Subject: Re: Was: Feedback on Scheduling? - How do you use yours? Date: Thu, 18 May 2006 11:24:58 +0200 Message-ID: <20060518092458.GB1800@ELSAMSW37164> References: <7383.1147799952@lap1.smtl.co.uk> <20060516184343.GA440@Zangband> <5763.1147808998@lap1.smtl.co.uk> <20060516211104.GA448@Zangband> <18671.1147851682@lap1.smtl.co.uk> <20060517100438.GA2540@ELSAMSW37164> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fgekb-0005IU-H8 for emacs-orgmode@gnu.org; Thu, 18 May 2006 05:24:57 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fgeka-0005IE-Ja for emacs-orgmode@gnu.org; Thu, 18 May 2006 05:24:57 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fgeka-0005IB-Ev for emacs-orgmode@gnu.org; Thu, 18 May 2006 05:24:56 -0400 Received: from [193.120.211.34] (helo=dspsrv.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Fgend-00044G-TN for emacs-orgmode@gnu.org; Thu, 18 May 2006 05:28:06 -0400 Received: from [145.36.45.123] (helo=localhost) by dspsrv.com with asmtp (Exim 3.36 #1) id 1FgekZ-00041m-00 for emacs-orgmode@gnu.org; Thu, 18 May 2006 10:24:55 +0100 Content-Disposition: inline In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org 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.