emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Tim O'Callaghan" <tim.ocallaghan@gmail.com>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Org-mode versus Taskpaper - now for real
Date: Thu, 3 Apr 2008 18:22:53 +0200	[thread overview]
Message-ID: <3d6808890804030922k7fbaddafw3abaeac277dfd500@mail.gmail.com> (raw)
In-Reply-To: <0277B507-1486-4172-B1C6-1B73B84148DD@science.uva.nl>

To be honest when i first read it i thought it was a good idea. I saw
it as an extension of your splitting the big org file into the smaller
include files in the git repo.

>
>  What people miss when they are new to Org-mode is this:
>
>  Don't try to set up the "final" task managing system from the
>  start.  Because you have no idea yet what your system should look
>  like.  Don't set up many TODO states and logging initially,
>  before you actually have a feeling for what you working flow is.
>  Don't define a context tag "@computer" just because David Allen
>  has one, even though you are sitting at a computer all the time
>  anyway!  Start by creating and managing a small TODO list and
>  then develop your own system as the needs arises.  I wrote
>  Org-mode to enable this development process.
>

I think a way to address this in Org-Mode would be to start with a
chapter explaining what Org-mode is about and an example of how to use
the very basic TODO functionality. A single file TODO project,
probably based around cooking a recipe or something. Then in later
chapters you could apply the new feature(s) described by expanding on
the initial use-case.

Also with that use-case as a baseline we could generate an appendix of
usage/best practices or whatever, for the clock-in-out-people, the
print every day people, one big ass text file people etc....

I for one would be interested in knowing how other people use
org-mode, and always on the look out for interesting tweaks.

Tim.

      parent reply	other threads:[~2008-04-03 16:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 10:28 Org-mode versus Taskpaper - now for real Carsten Dominik
2008-04-01 11:39 ` Rainer Stengele
2008-04-01 14:30 ` Russell Adams
2008-04-01 15:52 ` Eddward DeVilla
2008-04-01 19:11   ` Carsten Dominik
2008-04-03  9:55   ` Rick Moynihan
2008-04-03 14:26     ` Manish
2008-04-03 15:14       ` Rick Moynihan
2008-04-03 16:59         ` Bastien
2008-04-03 17:27           ` Rick Moynihan
2008-04-04  9:26             ` Bastien
2008-04-04  9:12         ` Carsten Dominik
2008-04-04 12:20           ` Egli Christian (KIRO 433)
2008-04-04 12:38             ` Carsten Dominik
2008-04-07 15:14           ` Carsten Dominik
2008-04-03 16:26       ` Joel J. Adamson
2008-04-03 17:39         ` Rick Moynihan
2008-04-04  7:49       ` Carsten Dominik
2008-04-03 23:28     ` Jason F. McBrayer
2008-04-01 23:05 ` Sven Bretfeld
2008-04-02  2:54   ` Clint Laskowski
2008-04-03 16:22 ` Tim O'Callaghan [this message]

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=3d6808890804030922k7fbaddafw3abaeac277dfd500@mail.gmail.com \
    --to=tim.ocallaghan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).