emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Pete Phillips <pete@smtl.co.uk>
To: Tim O'Callaghan <timo@dspsrv.com>, emacs-orgmode@gnu.org
Subject: Re: Was: Feedback on Scheduling? - How do you use yours?
Date: Wed, 17 May 2006 08:41:22 +0100	[thread overview]
Message-ID: <18671.1147851682@lap1.smtl.co.uk> (raw)
In-Reply-To: Message from Tim O'Callaghan <timo@dspsrv.com> of "Tue, 16 May 2006 23:20:02 +0200." <20060516211104.GA448@Zangband>


[Once more - but to the list this time!  :-( ]


Tim O'Callaghan <timo@dspsrv.com> wrote:

    Tim> Its also interesting that you use tags for GTD context. This is
    Tim> the way i use tags, and i have been wondering if anyone else
    Tim> used them like this.

I'm glad - I was in discussion with Carsten for a while regarding
org-mode, when he came up with this brilliant idea of tags - as soon as
he proposed it, I could see that it would fit into my GTD system
straight away (I moved from a Zaurus list manager to org-mode+hipster
last August, but have been using GTD since the original hardback book
came out).

    Tim> An interesting idea, one that i was kicking about for a bit
    Tim> when i was using a hipster style PDA. I was thinking about
    Tim> generating XSLFO or SWF based templates, and merging the
    Tim> information into the XML template for printing. XSLFO is a
    Tim> pain, so i went for SWF, which is a pain but less so. SWF has
    Tim> the advantage of being scalable if designed properly, and
    Tim> supported by inkscape, which makes creating templates easy. I
    Tim> experimented with ImageMagick and an SWF based templates for
    Tim> automatic processing. I got an experimental SWF template from
    Tim> all things hipster: diyplanner.org. Unfortunately ImageMagick
    Tim> did not support SWF well enough for me to want to continue :(

Basically I used lyx to design the template and then exported it to
latex to see what I needed to add from the perl script. I have a bit of
experience with XML and XSL (our woundcare journal,
www.worldwidewounds.com, is prepared using docbook XML) but I have never
got to grips with the FO model.

    Tim> In the end i opted for a paperless system.

No good for me as I need something with me all the time. I find the PDA
too slow, and the HPDA fast and flexible. Combining my laptop org-mode
with HPDA has been terrific (for me - I readily acknowledge that this is
a game of horses for courses).

    Tim> I'd be interested to hear how other org users are implementing
    Tim> GTD. If for nothing else that to be able to cherry pick ideas
    Tim> that i can incorporate into my system.

Me also.

    Tim> My system is based around one big org mode file for personal
    Tim> stuff and one for work. I can edit the file in other editors
    Tim> (such as the one on my smartphone) and search for GTD context
    Tim> via tags. The symbol :TAGNAME: is unique enough to search on
    Tim> when i need context, and works to find tagged lines using every
    Tim> editor i know of.

Yep. By the way, you can also set up a shell script to mail your file to
a gmail account every night, so you have unlimited (well, almost)
backupand archive. I set up a special archive gmail account just for
this. with 2.?? Gb of space, I won't be running out of space soon.

    Tim> External editors do not support the org mode 'file:'
    Tim> references, so i am strict about keeping only Next Actions and
    Tim> possible Next Actions in the org file. I keep reference
    Tim> material in a another appropriately named file in the same
    Tim> directory.

I keep the lot in one big file. That's the advantage of using outline
mode - you can collapse gobs of text into nothing just by pressing the
<TAB> key. Less to keep track of and remember, and makes the perl script
-> HPDA doable.

    Tim> I also make sure the context tags and the text of the item will
    Tim> inform me of the project they are related to. So I don't need
    Tim> the reference material unless referred to by the text of the
    Tim> Next Action, and then only because it does not fit in one line.

Yep - I need to make sure that the headline has enough info so that when
printed onto the HPDA I can understand/recall what it relates to.

Regards,
Pete

Tim.

  reply	other threads:[~2006-05-17  7:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16  8:26 Feedback on Scheduling? Carsten Dominik
2006-05-16 17:19 ` Pete Phillips
2006-05-16 18:43   ` Tim O'Callaghan
2006-05-16 19:49     ` Pete Phillips
2006-05-16 21:20       ` Was: Feedback on Scheduling? - How do you use yours? Tim O'Callaghan
2006-05-17  7:41         ` Pete Phillips [this message]
2006-05-17  8:10           ` Carsten Dominik
2006-05-17 10:04           ` Tim O'Callaghan
2006-05-17 13:59             ` Kevin Coates
2006-05-18  9:24               ` Tim O'Callaghan
2006-05-18 11:14                 ` Kevin
2006-05-17  9:15   ` Feedback on Scheduling? David Emery
2006-05-17  9:14     ` 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=18671.1147851682@lap1.smtl.co.uk \
    --to=pete@smtl.co.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=timo@dspsrv.com \
    /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).