emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: handling cyclic tasks (general question)
Date: Sun, 04 Nov 2007 11:42:45 +0000	[thread overview]
Message-ID: <874pg2ck3u.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87r6j7xjrt.fsf@makhector.hypnokush.org> (Stuart McLean's message of "Sat, 03 Nov 2007 11:32:06 -0700")

Hi Stuart,

Stuart McLean <makhector@gmail.com> writes:

> Following is an example of the setup I currently have. 

Your setup might be difficult to maintain because of its chronological
structure.  I don't know if other people use Org this way or have used
it this way, but I think it could be hard to maintain... usually your
Org files will be project-oriented (or task-oriented) and you will use
the agenda and timeline functions to display information time-wise.

But maybe I'm wrong here, or you may specifically need this structure.

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

> What I would like to know, are there more elegant solutions for
> accomplishing this? 

Usually, closed entries get archived at some point.  The general issue
you're raising here is: how to archive closed instances of cyclic tasks?

Here is how I do it: 

- I close the cyclic task
- I add a note if needed
- I archive the task with C-c C-x C-s
- I copy the task back at point with C-y

Then, instead of having the same task with loooongs notes under its
headline, I have several archived instances of the task with a note
for each of them.

I'm quite okay with the workaround above, but it has two drawbacks:

- it's safer to C-y immediately (otherwise you'll struggly to find the
  right thing to yank)

- each archived task has the same headline (which might be confusing
  when reviewing (?) your archives

I don't know if other people already came across the same need and other
workarounds.  

> Is anyone willing to share their particular setup, or examples of
> variations. I find my current setup a little cumbersome.

Argh... we definitely need to demonstrate different setups in the
tutorial section of http://orgmode.org :-/

-- 
Bastien

next prev parent reply	other threads:[~2007-11-04 10:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03 18:32 handling cyclic tasks (general question) Stuart McLean
2007-11-04 11:42 ` Bastien [this message]
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=874pg2ck3u.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --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

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