From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel J. Sinder" Subject: Re: Suggestion: Jump points Date: Wed, 11 Jul 2007 11:23:42 -0700 Message-ID: <4695202E.9060801@gmail.com> References: <468E11C4.50604@calicojack.co.uk> <6da9122d5b79844f2856186565289598@science.uva.nl> <468E1D59.6030006@calicojack.co.uk> <468E6DAF.1040100@calicojack.co.uk> <4694C483.2060708@calicojack.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I8gqp-0007gw-9x for emacs-orgmode@gnu.org; Wed, 11 Jul 2007 14:23:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I8gqn-0007g8-Kq for emacs-orgmode@gnu.org; Wed, 11 Jul 2007 14:23:46 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I8gqn-0007g3-DH for emacs-orgmode@gnu.org; Wed, 11 Jul 2007 14:23:45 -0400 Received: from sd-green-bigip-202.dreamhost.com ([208.97.132.202] helo=randymail-a9.g.dreamhost.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I8gqm-0004Zp-MI for emacs-orgmode@gnu.org; Wed, 11 Jul 2007 14:23:45 -0400 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: Scott Jaderholm Cc: org-mode , Rick Moynihan On 07/11/2007 08:28 AM, Scott Jaderholm wrote: > On 7/11/07, Rick Moynihan wrote: >> So here's a suggestion. Why not support jump points (or jump lines), >> which would be essentially be a syntactic marker that would tell >> org-mode to jump to a specific line within an outline when visiting from >> the agenda e.g. via follow mode. >> >> * My main project outline. >> blah blah blah... >> ... >> >> - [ ] do something >> - [ ] do this ++ >> - [ ] do something else > > Hi Rick, > > I'm guessing you have a really good reason for organizing your project > using lists and check boxes instead of TODOs and headings, in which > case this email isn't really useful--but, in the extremely unlikely > event that you don't, I thought I'd note how this becomes a non-issue > if you organize your work in the following way: > > * My main project outline > ** TODO do something > ** NEXT do this > SCHEDULED: <2007-07-12 Thu> > ** do something else > > If you schedule individual tasks, instead of projects, then the agenda > will take you right to your next item. If you schedule projects, then > it's easy to see what is the next item to be done because it says > NEXT. If I may jump in here, I'll add that go a little further to aid with multiple projects. I use two SEQ_TODO's like this: #+SEQ_TODO: TODO NEXT INPROGRESS WAITING | DONE CANCELED #+SEQ_TODO: PROJECT | COMPLETE Then my project trees (all in one file) look like this: * PROJECT My main project outline :Work: ** TODO do something ** NEXT do this SCHEDULED: <2007-07-12 Thu> ** TODO do something else ** WAITING someone else is working on this ** INPROGRESS Here's what I'm currently working on * PROJECT Another project ** NEXT next for another project ** TODO do anothre thing When I generate agendas, I can do a tags/TODO agenda on 'Work/PROJECT|NEXT'. Through indentation, the agenda visually groups everything so I can see what's next for each project. It looks something like this. PROJECT My main project outline :Work: .NEXT do this PROJECT Another project :Work: .NEXT next for another project This is great for a weekly review, to make certain all project have a defined NEXT action. A tags/TODO agenda that includes all TODO keywords will also group tasks by project, but will give broader scope. (One down-side to this is that M-S- on the first TODO after a PROJECT headline inserts a new PROJECT rather than a new TODO, which I have to then change. The alternative, of course, is to add at the end of the list for a project. Regards, Dan