On Dec 31, 2007 11:41 AM, Bastien <[EMAIL PROTECTED]> wrote:
> As this is the right time for resolutions, one single question: what
> are your top 3 GTD-wise (or more generally org-wise) resolutions for
> this upcoming year?
>
Mine:
1. Try to catch up with a small fraction of the new functionalit
> "Adam" == Adam Spiers <[EMAIL PROTECTED]> writes:
Adam> Thanks a lot for the feedback. I have read the book several
Adam> times but it was great to be reminded of his views on
Adam> priorities. Having said that, I think I would really struggle
Adam> to review on a regularly
Bastien ([EMAIL PROTECTED]) wrote:
> Hi folks,
>
> a great new year's eve to everybody. Special thanks to Carsten for
> another year of fun with org-mode - and thanks to all who make this
> mailing list worth reading it everyday !
Seconded!
> As this is the right time for resolutions, one singl
Hi folks,
a great new year's eve to everybody. Special thanks to Carsten for
another year of fun with org-mode - and thanks to all who make this
mailing list worth reading it everyday !
As this is the right time for resolutions, one single question: what
are your top 3 GTD-wise (or more generall
On Dec 31, 2007 10:45 PM, Adam Spiers <[EMAIL PROTECTED]> wrote:
> Adam Spiers ([EMAIL PROTECTED]) wrote:
> > OK. My setup is similar except that I allow for sub-projects -
> > projects within projects. As a result, projects are not uniquely
> > identified by their star level, so I explicitly mar
Adam Spiers ([EMAIL PROTECTED]) wrote:
> OK. My setup is similar except that I allow for sub-projects -
> projects within projects. As a result, projects are not uniquely
> identified by their star level, so I explicitly mark them with PROJECT
> which means I retain the ability to do keyword sear
(More Structured Procrastination... ;-)
Adam Spiers ([EMAIL PROTECTED]) wrote:
> And on top of that, I need a way of marking a "someday" or "maybe"
> task/project as already STARTED or WAITING etc., which is why I
> wrote:
>
> > - Priorities become truly orthogonal to workflow, e.g. if your
> >
Imagine I have a single project or task which I know will require
several sessions to complete. Before I get to the stage of analysing
it closely and breaking it down into sub-tasks, it would be good to
reserve some diary time in advance, so that I don't accidentally
accept other commitments for t
Pete Phillips ([EMAIL PROTECTED]) wrote:
> > "Adam" == Adam Spiers <[EMAIL PROTECTED]> writes:
>
> Adam> GTD methodology suggests having "someday" and "maybe" task
> Adam> buckets for things which you want to remember to do at some
> Adam> undetermined point in the future.
>
>
And another ...
http://www.adamspiers.org/cgi-bin/hg.cgi/org-atlantic/rev/eeeab6022608
# HG changeset patch
# User Adam Spiers <[EMAIL PROTECTED]>
# Date 1199109084 0
# Node ID eeeab6022608fcb4348ddadcd595b20b3a524ecc
# Parent fb36fb4548b2f886ef0ecb7fc14daaeca39762a4
fix org-agenda-skip-if typos
http://www.adamspiers.org/cgi-bin/hg.cgi/org-atlantic/rev/fb36fb4548b2
# HG changeset patch
# User Adam Spiers <[EMAIL PROTECTED]>
# Date 1199108855 0
# Node ID fb36fb4548b2f886ef0ecb7fc14daaeca39762a4
# Parent 5b1e541ddd0e043c55aea3e1e164bf115e01a4e9
fix org-agenda-skip-* docstrings
diff -r 5b1
Adam Spiers ([EMAIL PROTECTED]) wrote:
> Suppose that I have a sub-keymap for custom agenda commands with
> prefix 's', i.e. shortcuts 's1', 's2', 's3' and so on. I might invoke
> org-agenda, press 's', then change my mind and want to use another
> custom command instead. Currently, the only way
12 matches
Mail list logo
