From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Moynihan Subject: Re: Suggestion: Jump points Date: Wed, 11 Jul 2007 17:29:14 +0100 Message-ID: <4695055A.7010103@calicojack.co.uk> 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; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I8f50-00069J-18 for emacs-orgmode@gnu.org; Wed, 11 Jul 2007 12:30:18 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I8f4y-00068k-JT for emacs-orgmode@gnu.org; Wed, 11 Jul 2007 12:30:17 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I8f4y-00068f-Ck for emacs-orgmode@gnu.org; Wed, 11 Jul 2007 12:30:16 -0400 Received: from storm.bpweb.net ([83.223.106.8]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1I8f4x-0000mx-TK for emacs-orgmode@gnu.org; Wed, 11 Jul 2007 12:30:16 -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 Scott Jaderholm wrote: > On 7/11/07, Rick Moynihan wrote: > 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 Don't count on it :) > 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 Thanks for the suggestion, I can see how this structure might be better suited for this sort of thing, and I do structure much of my org-file like this, though I hadn't thought of using a NEXT keyword. I think my problem is that I sometimes find myself torn between outlines and lists/checkboxes. Lists/checkboxes have some advantages over outlines, though outlines are obviously more powerful. I find I tend to use lists/checkboxes for smaller tasks which are best done in sequence, and where I want to track the % of progress. Is this possible with outlines? e.g. 1. [X] Do this first 2. [X] Do this second 3. [ ] Do this collection of tasks third but in any order [66%] - [X] foo - [ ] bar - [X] baz 4. [ ] Do this fourth I might well take your suggestions on board though and see how I get on. This said I can still think of situations where I might want follow-mode in the agenda to move the point directly to a bookmarked\tagged jump-point within an outline. For example, I often write quite extensive notes within an outline heading, and sometimes it might be nice to jump straight to where you were editing. R.