From: Thomas Moyer <tommoyer@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Question about org-habit and agenda views
Date: Thu, 16 Aug 2012 10:28:21 -0400 [thread overview]
Message-ID: <CAJMnJ1Wb793B2y_-dhdFz+wZOjzJ770TVCSJkQpD8vbL7Hxtzg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
I have a set of habits that I do Monday through Friday (weekdays only) and
the best suggestion I have found for this is to have 5 individual TODOs
(one for each day). This seems to work well for the most part, but I have
found one minor annoyance that I can't find a solution for.
If I don't do one of the habits on Monday, that entry will appear as
overdue until the next week on Monday when it comes around again. Is there
a way to "hide" overdue habits? I don't want to mark it as DONE, since it
wasn't even when it was late.
As an example of what I current have, here is an excerpt for one habit:
** Notes
*** TODO (M) Refile notes
SCHEDULED: <2012-08-20 Mon ++1w>
:PROPERTIES:
:STYLE: habit
:END:
*** TODO (T) Refile notes
SCHEDULED: <2012-08-21 Tue ++1w>
:PROPERTIES:
:STYLE: habit
:END:
*** TODO (W) Refile notes
SCHEDULED: <2012-08-15 Wed ++1w>
:PROPERTIES:
:STYLE: habit
:END:
*** TODO (R) Refile notes
SCHEDULED: <2012-08-16 Thu ++1w>
:PROPERTIES:
:STYLE: habit
:END:
*** TODO (F) Refile notes
SCHEDULED: <2012-08-17 Fri ++1w>
:PROPERTIES:
:STYLE: habit
:END:
So if I miss Monday, when I open my agenda on Tuesday, I currently see two
entries for Refile notes. Ideally, I would like to only see the one for
Tuesday, and then when the following Monday rolls around, I should see the
Monday entry again, with the consistency graph showing that I missed last
Monday.
Thanks for the help!
-Tom
--
Thomas Moyer
tommoyer@gmail.com
[-- Attachment #2: Type: text/html, Size: 2013 bytes --]
next reply other threads:[~2012-08-16 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 14:28 Thomas Moyer [this message]
2012-08-16 15:23 ` Question about org-habit and agenda views Jonathan Leech-Pepin
2012-08-17 16:15 ` Tomas Grigera
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=CAJMnJ1Wb793B2y_-dhdFz+wZOjzJ770TVCSJkQpD8vbL7Hxtzg@mail.gmail.com \
--to=tommoyer@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).