From: Stuart McLean <makhector@gmail.com>
To: emacs-orgmode@gnu.org
Subject: handling cyclic tasks (general question)
Date: Sat, 03 Nov 2007 11:32:06 -0700 [thread overview]
Message-ID: <87r6j7xjrt.fsf@makhector.hypnokush.org> (raw)
Hi,
Following is an example of the setup I currently have. What I am
interested in is how other members of the group might more elegantly
(or just differently) handle something similar.
* 2007
** January
...
** October
** November
each date has the following within it, example:
** November
** 2007-11-01
*** Todo
:PROPERTIES:
:CATEGORY: todo
:END:
**** TODO something
**** TODO something else
*** Work
:PROPERTIES:
:CATEGORY: work
:END:
**** Work I did <2007-11-01 Thu 08:00>--<2007-11-01 Thu 16:00>
1. work A
2. work B
3. etc
*** Exercise
:PROPERTIES:
:CATEGORY: exercise
:END:
**** exercise that I did
Now, at the end of each month, e.g 2007-11-30, I have a heading on the
same level called Cyclic Todo. These contain things that I need to do
everyday, and need to remember to do everyday. I end each with a
closing note when I do them. The thing is some of the details that I
wish to record in the closing note are long and would clutter up the
heading, so I add a hyperlink back to the date (e.g 2007-11-01) and
record the info there under the proper category (usually Exercise, but
you can generalize from there, it could be applied to something else.)
What I would like to know, are there more elegant solutions for accomplishing this? Is anyone willing to share their particular setup, or examples of variations. I find my current setup a little cumbersome.
Thanks, and sorry for the long post.
Stuart
next reply other threads:[~2007-11-03 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 18:32 Stuart McLean [this message]
2007-11-04 11:42 ` handling cyclic tasks (general question) Bastien
2007-11-04 21:38 ` Stuart McLean
2007-11-04 22:34 ` Bastien
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=87r6j7xjrt.fsf@makhector.hypnokush.org \
--to=makhector@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).