emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eddward DeVilla" <eddward@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: RE: Another GTD question.
Date: Sat, 21 Oct 2006 19:39:58 -0500	[thread overview]
Message-ID: <b71b18520610211739n4accda8bw8bfd2ec203181b4b@mail.gmail.com> (raw)
In-Reply-To: <b71b18520610211738s297f8f79u227d2ce32e10d2d9@mail.gmail.com>

On 10/21/06, Christopher Kuettner <ckuettner@gmail.com> wrote:
> Aside from that...
> What is the basic design model for org-mode?  What is org supposed to
> be?  Where it is headed? I thought I  got an outliner with
> dates-capabilities.  No it's almost a full fledged publishing platform...
> I think you did a terrific job so far.  Maybe you have to make some
> fundamental decisions here...

Those are some interesting questions.  I certainly can't answer any of
them, but I don't know one aspect of Org that I hope is maintained.
It's really flexible.  Kind of like perl.  It has a lot of little
nifty features that you can use to manage and organize information (to
tasks, or whatever) and use can use any subset you want.  You can
learn it incrementally.  (...as I have.  It sound popular but I
haven't even touched the publishing...)  None of the features really
require the use of any other feature except maybe agenda and agenda is
just a flexible interface for gathering the information marked and
managed by the other features.  (Dates, tags, Todo state...)  Yet all
of the features work well together.  There's more that one way to do
most things.

I don't really understand GTD, elisp or project management that I
would try to guess a good direction for Org-mode, but I do hope it is
able to maintain a design where you can pick and choose the features
and assemble them as they suit you instead of trying to impose a
framework or style.

And yes, Carsten and company of done an excellent job.  For all I've
pestered him and the list, I don't say that enough.  I just picked
org-mode because I was looking for a replacement an orphaned outliner
that I depended on.  Org turned out to be better in many ways and has
since surpassed it in all ways.  It's changed how I manage list,
projects, todo and information in general.  I'm actually excited to
see how it will grow.  You've done great.

  parent reply	other threads:[~2006-10-22  0:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 20:03 Another GTD question Alex Bochannek
2006-09-27 12:39 ` Charles Cave
2006-09-29 10:07   ` Christopher Kuettner
2006-09-30  5:25   ` Alex Bochannek
2006-09-30 11:28     ` Carsten Dominik
2006-10-01 14:41       ` Piotr Zielinski
2006-10-02  8:58         ` Chris Lowis
2006-10-14  4:44       ` Alex Bochannek
2006-10-01 23:54     ` Charles Cave
2006-10-14  4:53       ` Alex Bochannek
2006-09-27 14:18 ` Uwe Jochum
2006-10-04 16:11 ` Carsten Dominik
2006-10-04 17:11   ` Piotr Zielinski
2006-10-20  7:54     ` Carsten Dominik
2006-10-21 20:54       ` Christopher Kuettner
     [not found]         ` <b71b18520610211738s297f8f79u227d2ce32e10d2d9@mail.gmail.com>
2006-10-22  0:39           ` Eddward DeVilla [this message]
2006-10-23  6:10             ` Carsten Dominik
2006-10-23  7:21               ` Xiao-Yong Jin
2006-10-23  7:36                 ` Carsten Dominik
2006-10-23 20:30                   ` Xiao-Yong Jin
2006-10-23 13:24               ` Eddward DeVilla
2006-10-22 11:28         ` Pete Phillips
2006-10-05 13:01   ` Jason F. McBrayer

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:

  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=b71b18520610211739n4accda8bw8bfd2ec203181b4b@mail.gmail.com \
    --to=eddward@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).