From: Bastien <bzg@gnu.org>
To: Fletcher Charest <fletcher.charest@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Scheduled tasks: total time since last DONE
Date: Mon, 28 Jul 2014 16:10:35 +0200 [thread overview]
Message-ID: <874my1z98t.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAGk6a7n0kr_4Xt3vYR=ygCTgY4MutnmTRVKhSkVzGgcQoHUk5Q@mail.gmail.com> (Fletcher Charest's message of "Tue, 15 Jul 2014 22:55:55 +0200")
Hi Fletcher,
Fletcher Charest <fletcher.charest@gmail.com> writes:
> This way I could see it's been 7 days I didn't do it, and tasks would
> be better organized in the agenda. RIght now, a task that I have to
> do on a weekly basis never has a number greater than '6x', and even
> if it hasn't been done for months, it still appears on the bottom of
> the list in the agenda, with a small number.
>
> So is there a way to correct this?
Not really.
> How do you proceed?
I distinguish "repeating tasks" and "nagging tasks".
Cleaning the kitchen is typically a nagging task: not because some
people find it boring (no comment) but because you can't do the next
one before doing the previous one*... a repeating task is typically a
course at the uni: you can attend the next one without attending the
previous one, and in this case, the current behavior of Org makes
sense.
So, for nagging tasks, I simply don't use a repeater, this way the
task is always nagging me :) When it's done, I reschedule it using
C-c C-s . S-<down> for the next week. And voilà.
HTH,
* A joke of a good friend of mine:
« See you next time!
- Mhh.. will be difficult to see each others before this one. »
--
Bastien
next prev parent reply other threads:[~2014-07-28 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 20:55 Scheduled tasks: total time since last DONE Fletcher Charest
2014-07-16 15:33 ` J. David Boyd
2014-07-28 14:10 ` Bastien [this message]
2014-07-28 15:45 ` Sebastien Vauban
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=874my1z98t.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=fletcher.charest@gmail.com \
/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).