From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Subject: Re: Was: Feedback on Scheduling? - How do you use yours? Date: Thu, 18 May 2006 13:14:45 +0200 Message-ID: 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> <20060518092458.GB1800@ELSAMSW37164> Reply-To: kevin.coates@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FggSw-0000lL-SZ for emacs-orgmode@gnu.org; Thu, 18 May 2006 07:14:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FggSs-0000l9-DJ for emacs-orgmode@gnu.org; Thu, 18 May 2006 07:14:50 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FggSs-0000l6-6b for emacs-orgmode@gnu.org; Thu, 18 May 2006 07:14:46 -0400 Received: from [64.233.166.181] (helo=py-out-1112.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FggVw-0004bX-Uh for emacs-orgmode@gnu.org; Thu, 18 May 2006 07:17:57 -0400 Received: by py-out-1112.google.com with SMTP id i49so515062pyi for ; Thu, 18 May 2006 04:14:45 -0700 (PDT) In-Reply-To: <20060518092458.GB1800@ELSAMSW37164> Content-Disposition: inline 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 > 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? Here you go (not sure what'll happen to the formatting). And this is my first piece of perl, so be gentle ;-) #used on org files that have the structure: # * Projectname :Project: # ** NextActionA :Context1: # ** NextActionB :Context2: # %hash_TagsLine: hash with keys=3Dtags # @{$hash_TagsLine{$tag}: set of arrays, one for each tag whose contents are all items with that tag # %actionsperproject: hash with keys=3Dproject name and values =3D number of next actions for each project # @emptyprojects: array with a list of the empty projects @ARGV =3D "d:/Documents/txt/Next Actions Outline.org"; #hard coded org file while ($line=3D<>){ #go through each line of org file chomp; # remove line breaks foreach $tag ($line =3D~ /:(\w+):/g){ # find the tag in the current lin= e $line =3D~ s/:$tag://; # remove the tag =09$line =3D~ s/\*//g; # remove "*" =09$line =3D~ s/^\s+//; # remove leading spaces =09$line =3D~ s/\s+$//; # remove trailing spaces =09$line =3D~ s/\s+/ /g; # replace every group of one or more spaces with a single space if ($tag eq "Project") =09 { =09=09if ($nextactions eq "0"){push (@emptyprojects, "$projectname")}; #if we get to a Project and nextactions still equals zero, then we have an empty project =09push @{$hash_TagsLine{$tag}}, "$line"; #add this line to the project list array =09$projectname =3D "$line"; #keep the name of the project for appending to the next actions =09=09$nextactions =3D 0; # as this is a new project, reset the next action= s to zero } else { #if this is not a new project =09 $nextactions =3D $nextactions + 1; #it's a next action so update t= he count =09 $actionsperproject{$projectname} =3D "$nextactions"; #update the hash with the latest next actions count for this project =09 $encodedline =3D $line." [$projectname]";=09#add the project name to the next action =09 push @{$hash_TagsLine{$tag}}, "$encodedline"; #add to this tag's = array } } } > 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. Yup, yak shaving is something I have to admit to. Though per "pure" GTD, a reminder to me two weeks in advance of a birthday that I should sort out a card and present should appear at the right time on my next actions list, rather than my calendar. Kevin