emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Charles Philip Chan <cpchan@bell.net>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Using org-mode as day planner
Date: Fri, 10 Aug 2012 07:46:36 -0400	[thread overview]
Message-ID: <BLU0-SMTP366D696F1832DAE9CAE320BBB30@phx.gbl> (raw)
In-Reply-To: <5023F648.1060701@jugband.net> (Jack Erwin's message of "Thu, 09 Aug 2012 11:41:28 -0600")

[-- Attachment #1: Type: text/plain, Size: 2911 bytes --]

Jack Erwin <jack@jugband.net> writes:

Hello Jack:

> I am in the process of trying out org-mode after a long stint with
> planner.el.  The most obvious difference here is that planner.el uses
> "day pages" that keep a running list of tasks versus the more dynamic
> nature of org which collects them from a set of arbitrary .org files.

I am a planner refugee from a few years back too. I find that my first
hurdle was to get rid of the notation that day pages must be physical
instead of emphemeral.

> While I like the org approach quite a bit, I still miss having a place
> to record the events and notes of the a day, for use in a
> weekly/monthly review.

There are many ways to do this and it is up to you imagination. Such as
by using a "date tree" or a combination of "inactive time stamps" and
tags. I personally have a ":Review:" tag in my capture templates for new
items and cleared after review. My day and weekly pages are Agenda views
that can be called up with one hot key either from Emacs or from my root

I think the term "Agenda View" really throws new users off, because it
is not just for Agendas, but really just a generic aggregator. For
example in my daily Agenda, I have the following sections:

   1. An aggregated Inbox for unfiled items in my org files and dired
      link to my inbox directory.

   2. A section for "Late Deadlines".

   3. A Section for "Wait For" items.

   4. A section for Sticky notes and other items that I deemed hot.

   5. A section from current working files and notes.

   6. A 1 day Agenda View for Agenda, scheduled items, deadline items,
      habits, weather, etc.

   7. A "Started Actions" section for items that I am working on (todo
      keyword "STARTED".

   8. A "Next Actions" List (todo keyword "NEXT").

   9. A list of my Projects

  10. A section for "Stuck Projects".

  11. A list for my Actions minus started and next (todo keyword TODO).

  12. A list of items that are candidates to be archived.

Of course I also have a number of Agenda Views for context lists.

The key here is really to take some time to set up your Agenda Views and
Capture Templates.

You should really read this section on worg:


to get some more ideas. Also I find the following links very helpful (my
setup is based on that):



Another thing your should take advantage of is org-protocol. I
personally have 2 shell scripts for "capture" and "store-link" which I
have added as actions in my file manager, my root menu and of course I
used org-protocol in Firefox.

"The move was on to 'Free the Lizard'"

  -- Jim Hamerly and Tom Paquin (Open Sources, 1999 O'Reilly and Associates)

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2012-08-10 11:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 17:41 Using org-mode as day planner Jack Erwin
2012-08-10  8:09 ` Bastien
2012-08-10 12:46   ` John Hendy
2012-08-10 13:47     ` Jonathan Leech-Pepin
2012-08-11  9:34     ` Bastien
2012-08-12 15:48       ` John Hendy
2012-08-13 18:20         ` Martin Pohlack
2012-08-13 18:43           ` Jambunathan K
2012-08-13 18:51             ` Bastien
2012-08-14  8:11         ` Bastien
2012-08-10 11:46 ` Charles Philip Chan [this message]
2012-08-10 12:28   ` Charles Philip Chan

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=BLU0-SMTP366D696F1832DAE9CAE320BBB30@phx.gbl \
    --to=cpchan@bell.net \
    --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).