emacs-wiki-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[emacs-wiki-discuss] Re: Planner mode and Info


From: Sacha Chua
Subject: [emacs-wiki-discuss] Re: Planner mode and Info
Date: Thu, 12 Aug 2004 00:21:48 +0800
User-agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux)

Tim O'Callaghan <address@hidden> writes:

> I'm not much of a lisp hacker, so i can only suggest something like:
> (add-to-list 'Info-directory-list (expand-file-name planner-root)

The planner-root might be a bit difficult. I guess we really should
just have a proper Makefile that bytecompiles stuff and installs them
into the right directories. Does anyone already have one of those
lying around? =)

>>>#A1    _ Make some tea
>>>- #B1   _ buy some tea bags
>>>-- #C1    _ go to shops for tea bags
>>>-- #c2    _ pick some biscuits up?
>>>- #B2   _ boil water in kettle - here is (HowToBoilWater)
>> I have a note about hierarchical tasks somewhere on
>> http://www.emacswiki.org/cgi-bin/wiki/PlannerModeMethods, I think. =)
> Yeh i saw that

Mm. Yeah, normally I'd think of making just the lowest level actual
tasks. It would be nice if we could find an elegant way to deal with
this, though.

> I cannot say how it would work in the code, but having the tree
> auto-renumber, with the number re-starting at each new branch. Then
> you could reference it with a dot notation. e.g.

The numbers aren't actually that important any more because
renumbering makes it difficult to rely on numbers for future task
references. Does anyone actually use task numbers in links? <grin>
Well, I guess if you're referring to past stuff...

> I want to do a kind of tree-like functional de-composition of my
> tasks, though it would be nice to be able to reference them from
> notes, or the daily tasks page.

Mmmmmm... Well, you could already use headings like so:

* Heading 1
** Heading 2
*** Heading 3
**** Heading 4
#A0 _ Some task
**** Another heading 4
#A0 _ Another task

although I suppose that's not very clear...

Okay. Let's say we have your

#A0 _ Task A
 #A0 _ Task B
  #A0 _ Task C
  #A0 _ Task D
 #A0 _ Task E
  #A0 _ Task G
  #A0 _ Task H
#A0 _ Task I

What operations should you be able to perform? Can you write me the
manual for it? <grin>

> I suppose i could also use it to help categorize my wiki
> information, like a table of contents.

You can already do this with

* Heading 1 ... and so forth. =)

Check out the wonderful allout.el so that you can collapse your
trees easily.

> I'm not sure to be honest. Using a reference link? say todays task is:
> #(TaskPool#A1.B1) - which translates to

For day pages, we can use task IDs to simplify things. So it'll be like

#B0 _ Buy some tea bags {{Tasks:<somenumber>}} (TaskPool)

> I'm still a newbie with the planner, so my suggestion is borne out
> of wanting to mold planner to my way of thinking, rather than having
> it mold me into its... which may not be such a bad thing.

In fact, it is the perfect thing. I am of the firm belief that
software should fit the way we work. <grin>

-- 
Sacha Chua <address@hidden> - open source geekette
interests: emacs, gnu/linux, making computer science education fun
wearable computing, personal information management
http://sacha.free.net.ph/ - PGP Key ID: 0xE7FDF77C




reply via email to

[Prev in Thread] Current Thread [Next in Thread]