From: "Daniel J. Sinder" <djsinder@gmail.com>
To: Scott Jaderholm <jaderholm@gmail.com>
Cc: org-mode <emacs-orgmode@gnu.org>, Rick Moynihan <rick@calicojack.co.uk>
Subject: Re: Suggestion: Jump points
Date: Wed, 11 Jul 2007 11:23:42 -0700 [thread overview]
Message-ID: <4695202E.9060801@gmail.com> (raw)
In-Reply-To: <b2e202b30707110828h195a0ebfsd6055b93366d347@mail.gmail.com>
On 07/11/2007 08:28 AM, Scott Jaderholm wrote:
> On 7/11/07, Rick Moynihan <rick@calicojack.co.uk> 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-<RET> 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
next prev parent reply other threads:[~2007-07-11 18:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 22:01 definition lists in org-mode Eddward DeVilla
2007-07-06 9:56 ` Rick Moynihan
2007-07-06 10:34 ` Carsten Dominik
2007-07-06 10:45 ` Rick Moynihan
2007-07-06 12:43 ` Carsten Dominik
2007-07-06 15:52 ` Eddward DeVilla
2007-07-06 16:28 ` Rick Moynihan
2007-07-06 17:22 ` Carsten Dominik
2007-07-11 11:52 ` Suggestion: Jump points Rick Moynihan
2007-07-11 14:51 ` Eddward DeVilla
2007-07-11 15:20 ` Rick Moynihan
2007-07-11 15:45 ` Eddward DeVilla
2007-07-12 12:24 ` Carsten Dominik
2007-07-11 15:28 ` Scott Jaderholm
2007-07-11 16:29 ` Rick Moynihan
2007-07-11 18:23 ` Daniel J. Sinder [this message]
2007-09-03 16:21 ` Carsten Dominik
2007-07-06 15:33 ` definition lists in org-mode Eddward DeVilla
2007-07-06 15:25 ` Eddward DeVilla
2007-07-06 10:44 ` Carsten Dominik
2007-07-06 15:43 ` Eddward DeVilla
2007-07-06 17:25 ` 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=4695202E.9060801@gmail.com \
--to=djsinder@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jaderholm@gmail.com \
--cc=rick@calicojack.co.uk \
/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).